Submitted by ADobkin on Fri, 10/16/2009 - 13:54
At some point recently, the Edit Web Pages features stopped working on our server. It may correlate to a recent update, such as Webmin 1.490 or Virtualmin 3.73, but I don't know that for sure. But it did work within the past month, and now it only displays the HTML code, not the rendered WYSIWYG text with toolbars.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 10/16/2009 - 14:13 Comment #1
Which browser are you using there?
Also, if you open the javascript console or error console in your browser, do you see any messages logged when you open the HTML Editor?
Submitted by ADobkin on Fri, 10/23/2009 - 10:24 Comment #2
I mostly use Firefox 3.5.3 on Windows XP, but it is happening on mulitple browsers and multiple computers. The issue was actually reported by one of our clients, and I confirmed it on my end.
I'm not sure if this is related or not, but I get a bunch of these messages (and a lot of others) in the error console on that page:
Warning: The 'charCode' property of a keyup event should not be used. The value is meaningless. Source File: chrome://browser/content/browser.xul Line: 0
After trying it several times now, it looks like eventually, if I wait long enough, the editor will load correctly. I'm not sure if something has changed on the server side (since I recently updated to Webmin 1.493 and CentOS 5.4), or if I am just waiting longer now for the page to get past the errors and load the editor, but it does seem to be working now.
Submitted by JamieCameron on Fri, 10/23/2009 - 11:30 Comment #3
The HTML editor is made up a lot of image, javascript and CSS files, so can take a long time to load the first time you open it ..
It is faster to open if you navigate away from the editor page and then re-open it again?
Submitted by ADobkin on Sat, 10/24/2009 - 16:32 Comment #4
There must have been something going on with the server to slow it down, since it was not loading the editor at all before, even after several minutes. But since the updates and possibly a restart, it seems to be back to normal now.
Other than the JavaScript errors above (which I'm not sure if they are related), you can close this item.
Submitted by JamieCameron on Sat, 10/24/2009 - 19:08 Comment #5
Ok, cool .. those javascript warnings seem un-related to the HTML editor.
Submitted by Issues on Sun, 11/08/2009 - 01:29 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.