FCKConfig.GeckoUseSPAN is a boolean, so setting its value to a string is just wrong. On the other side FCKConfig.ProtectedSource is an object, so setting it to a pseudo boolean is again wrong. There are several samples in the default fckconfig.js file.
And most important: remember that FCKeditor is an HTML editor, so trying to use mixed html and custom XML tags with no namespace can lead to lots of problems, specially if you set it wrong
> FCKConfig.GeckoUseSPAN = false ; > -> and it DOES NOT work!!!
Then you have some problem in your browser or you're loading a cached version.
> FCKConfig.ProtectedTags This setting is aimed for tags that the browser has some trouble parsing. I don't think that this is your case.
> FCKConfig.ProtectedSource = ??? > -> OK, this one was my fault, but there is NO INFORMATION on how to set this or make it working, so i asked for further steps, didn't i? There are several samples in the config file, you just set up a regexp to protect the parts that you don't want the editor to touch.
And I repeat: FCKeditor is an HTML editor, if you try to use it with XML code then you have to do things carefully and even then it might not work as you expect because nobody has tried that thing before.
RE: Problems with Custom Tags!? :-(
RE: BUG - Problems with Custom Tags! :-(
RE: BUG - Problems with Custom Tags! :-(
On the other side FCKConfig.ProtectedSource is an object, so setting it to a pseudo boolean is again wrong. There are several samples in the default fckconfig.js file.
And most important: remember that FCKeditor is an HTML editor, so trying to use mixed html and custom XML tags with no namespace can lead to lots of problems, specially if you set it wrong
RE: BUG - Problems with Custom Tags! :-(
RE: BUG - Problems with Custom Tags! :-(
> -> and it DOES NOT work!!!
Then you have some problem in your browser or you're loading a cached version.
> FCKConfig.ProtectedTags
This setting is aimed for tags that the browser has some trouble parsing. I don't think that this is your case.
> FCKConfig.ProtectedSource = ???
> -> OK, this one was my fault, but there is NO INFORMATION on how to set this or make it working, so i asked for further steps, didn't i?
There are several samples in the config file, you just set up a regexp to protect the parts that you don't want the editor to touch.
And I repeat: FCKeditor is an HTML editor, if you try to use it with XML code then you have to do things carefully and even then it might not work as you expect because nobody has tried that thing before.
RE: BUG - Problems with Custom Tags! :-(
BUG! Problems with Custom Tags!? :-(
RE: Problems with Custom Tags!? :-(