-
☆ A M B ☆
- 24,524 Posts
I just noticed that I’m getting a double editor when editing documents, one above the other. The entire editor, menu bar and all. I haven’t checked to see if both are actually editing the content though.
What OS and browser? And does it happen pretty consistently? Umm...do you have a test server I can log into? Wouldn’t mind checking this out. Sounds like a pretty weird bug!
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
I had this befor when updating I had 2 fck plugins running deleted both and reinstalled (copy/paste) the plugin.
That solved that isseu
Quote from: Dimmy at Aug 23, 2005, 11:33 AM
I had this befor when updating I had 2 fck plugins running deleted both and reinstalled (copy/paste) the plugin.
That solved that isseu
Heh heh...it’s always something simple, ain’t it!
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Jeff,
Another Strange thing with FCK is that it’s converting <quickedit:pagetitle /> into <pagetitle></pagetitle> but if I should add <asp:label /> it does not convert it.
Is there a way to prevent it from modifying those tags?
Quote from: xwisdom at Aug 23, 2005, 03:00 PM
Jeff,
Another Strange thing with FCK is that it’s converting <quickedit:pagetitle /> into <pagetitle></pagetitle> but if I should add <asp:label /> it does not convert it.
Is there a way to prevent it from modifying those tags?
I’ll do a little research, but I’m pretty sure there’s a setting in the fckconfig.js file that’ll fix that problem. I think it’s FCKConfig.FormatSource but I can’t say for certain. I’ll find out and get back to you. This might be one of those things that needs to be added as an editor configuration option.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Well...it would seem that FCKeditor thinks of the tag as an XML tag and thus wants to close the tag. As an experiment, I tried setting EnableXHTML and EnableSourceXHTML to false and IE kept the tag as is but added a closing tag to it as well as a doctype classification to the beginning....not good! I then set these back to true and tried setting FormatSource and FormatOutput to false...no real change there. Sigh! This is definitely an issue with FCKeditor itself and there doesn’t appear to be any real fix at the moment. I searched the forums on the FCKeditor SourceForge site and didn’t get any answers...although there were other posts made by others with a similar question. I’m not sure if we can really rely on FCK to support tags like this since they’re so damn close to being XML tags. It’s flaky at best. It even turned this:
Into this:
So...on that note...looks like we need to re-evaluate the use of this tag in FCK. BTW, it works great in TinyMCE.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Jeff,
Have you tried dropping the creator of FCK a line? Maybe he can help?
Quote from: xwisdom at Aug 23, 2005, 05:14 PM
Jeff,
Have you tried dropping the creator of FCK a line? Maybe he can help?
Yeah, I’ll send a message on over to him. Hopefully we can get an answer shortly.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
-
☆ A M B ☆
- 24,524 Posts
It looks like if you do an upgrade and just accept all the default snippet and plugin installations you’ll get a double FCKEditor installation. Maybe the installer should disable all of the snippet and plugin install options if it’s an upgrade?