I seem to have a problem with the FCK Editor, I am adding pages to my content module. The editor though seems to have a mind of its own. I was using 2.02 before and kept copies of the pages that I had created in html. The pages included text, images, and paypal code. It worked fine in 2.02. I thought I could just simply add the pages to Content module pages after installing the 2.10 but thats not been the case. I added an html page to Source and found it displayed wrong and text etc was moved around on its own accord, an image near the top of the page was moved to the bottom, things like that. I decided to input my pages from scratch actually using the editor thinking the problem would be solved, but it wasn't. There was an issue with font size, and even though I fixed it in style.css, a bit later after I had added more text etc., it started changing the font size again, even though in source it is still correct. I have just spent 7 hours playing around with one page trying to get it to load right, and its just not happening, just when I thought I was getting there, it changed part of the text again. Is it possible to remove the FCK editor and install the editor that was in 2.02?
It would help to have some examples of your problem so we could better determine what's happening. In general, FCKeditor doesn't change the HTML source you enter, though it can generate compliant HTML if you enter it on the WYSIWYG function.
However, the problem may have nothing to do with FCKeditor, per se. RN 2.10 supports compliant HTML, and that could be causing these issues. Again, seeing the HTML you saved would help.
You can disable the editor by changing the $advanced_editor setting in your config.php file. I'm not sure FCKeditor is a different version in 2.02, but you you could probably replace the includes/FCKeditor directory with an older 1.0 version from
Only registered users can see links on this board! Get registered or login to the forums!
Also, I installed a script for a client and found that it didn't display properly with IE 6.0. After checking the scripts home page, I saw that it required FF 2.0+ or IE 7+. Since IE 6 displayed it as XML, I realized that the script's HTML compliance caused the problem (another reason not to use IE...)! Simply removing one line of HTML that affected compliance enabled the script to work fine with IE 6.0.
Thanks for the help, I changed the setting for the editor to off, and I can add my pages easily now, my site is still W3C compliant too, so no problems now.
View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum