User login
July 19, 2010 - 3:54pm — Learned Vagrant
Several times in the last few days I've tried to post a comment and the text editor would not accept what I was typing. ??
Several times in the last few days I've tried to post a comment and the text editor would not accept what I was typing. ??
I've had similar issues going back awhile. Sometimes the editor just doesn't want to load appropriately. I end up refreshing the page until it does. I'm using Firefox 3.6.6.
Then it doesn't work, just so you know. Reload, or back and retry comment, usually works for me.
I've just installed Firefox 3.6.6 and it's just started happening for me too so it definately looks browser specific. Let's hope the next Firefox update fixes it. In the meantime like Mene says just refresh the page and it should load.
After the website update, I noticed the input box was a different color, and it loaded immediately. I had thought that perhaps the problem was fixed, but my next attempt after that required innumerable reloads to get it to show a cursor. Additionally, the times where it works the box is the same exact color as when it doesn't, while before the two boxes were different colors.
The editor is a different colour because the custom theming was lost when the website was upgraded.
The editor module we use is called FCKEditor, this has recently been completely rewritten as for version 3 and renamed CKEditor. By all accounts this new version of the editor is much lighter and faster. I'm planning to do some testing with this new version to see whether it woulld be suitable to upgrade the website with. If so hopefully that will solve most of the problems some people have been having.
Incidentally if you are having serious problems with the current editor you can always click the 'Switch to plain text editor' link just under the editor to switch it off.
Another trick which you can use in the browsers for some mobile devices which also don't load the editor properly is to click the 'Paste as plain text' toolbar button on the editor and then type into the window that appears.
Neut.. we have page compression enabled. Do you think that is interfering with the rendering of the editor?
I wouldn't have thought so. I was under the impression that page compression just combined and compressed all the css files referenced by the various page parts. The issues people seem to be having with the editor (and that I've experienced myself) seems more to do with various browsers or browser versions timing out on the editor initialisation.
It's possible but wouldn't be my first guess.