Page 1 of 1
News Module Editor Kills Firefox
Posted: Tue May 23, 2006 1:54 pm
by pgoneill
Firefox doesn't seem to like editing news. Always, at some point, FCKEditor causes Firefox to lock up. Generally it'll render half the page and part of one of the two WYSIWYG controls, but then it locks up. If FCKEditor is disabled, this doesn't happen. FCKEditor works, however, in every other context - just not in news...
Using CMSMS 0.12.1 (not sure on the PHP/MySQL versions, though they're probably recent). Perhaps an upgrade is in order...
Re: News Module Editor Kills Firefox
Posted: Tue May 23, 2006 3:16 pm
by calguy1000
You're probably reaching a php memory limit or something. I'm pretty sure this problem would reproduce if your templates had multiple content blocks, and you tried to edit a page.
Re: News Module Editor Kills Firefox
Posted: Tue May 23, 2006 3:39 pm
by pgoneill
Then why would it only affect Firefox and not IE.
Re: News Module Editor Kills Firefox
Posted: Tue May 23, 2006 3:48 pm
by tsw
My guess is it is hitting firefox memory limit.. fckeditor is pretty memory intensive blob of javascript
what version of FF are you using and have you tested with other computers..
I would disable fckeditor and use html or maybe tinymce or markdown to style text
Re: News Module Editor Kills Firefox
Posted: Tue May 23, 2006 4:32 pm
by pgoneill
Alright, I'll give another one a try. Thanks.
Quick question. The users would like the buttons that allow them to upload images and such and link to pages within CMSMS. Can that functionality be added to TinyMCE or is it only FCKEditor?
Re: News Module Editor Kills Firefox
Posted: Wed May 24, 2006 3:03 am
by Dr.CSS
calguy
how many content blocks would be too many?
this page has 5, it just takes a little longer to load than one with one or two content blocks...
just curious...
http://www.multiintech.com/index.php?page=niftycubes
mark
Re: News Module Editor Kills Firefox
Posted: Wed May 24, 2006 3:14 am
by calguy1000
mark
that depends on fckeditor and if it loads a new instance each time, if it does you'll run into all kinds of memory issues.
you can, however shut off the wysiwyg on a per content block basis.