Page 1 of 1
Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Mon Feb 16, 2009 6:58 pm
by MrLeeh
Hello,
I updated from 1.4.0 to 1.4.1 and realized that I can' t use the WYSIWYG Editor anymore. There are no menus or buttons. I have already checked if the editor is enabled. Could someone help in this because I can' t find a way getting it working again.
Thanks
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 3:59 am
by Don Chambers
From the backend, if you check "personal settings", is the wysiwyg editor enabled? The wysiwyg editor did change in 1.4, so there could be more to your problem, but I thought this simple question was a good place to start.
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 9:55 am
by garvinhicking
Hi!
Also make sure to refresh your browser cache? It might still have the old WYSIWYG files cached.
Regards,
Garvin
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 1:23 pm
by MrLeeh
Thx for the fast answer.
From the backend, if you check "personal settings", is the wysiwyg editor enabled?
Yes it is enabled. I double checked it all the time.
Also make sure to refresh your browser cache?
I refreshed my browser cache as well.
The wysiwyg editor did change in 1.4
Maybe there is a way to check if the new wysiwyg editor is installed successfully so I have a point to start my research.
Thx
MrLeeh
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 1:29 pm
by garvinhicking
Hi!
You could use Firefox and open the Javascript error console and/or Firebug to check which files are loaded, and if you have any 40x errors.
Regards,
Garvin
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 1:51 pm
by MrLeeh
You could use Firefox and open the Javascript error console and/or Firebug to check which files are loaded, and if you have any 40x errors.
I did it now and got the following warning messages:
1. unknown property 'behavior'. declaration ignored
source: /serendipity_admin.css
2. error processing the property 'filter' declaration ignored.
source: /htmlarea/Xinha.css
I guess it has something to do with the second error. I read Xinha is the new wysiwyg editor.
When I klick on the error link I get the following code:
Code: Select all
.htmlarea .toolbar .buttonDisabled img {
filter: gray() alpha(opacity = 25);
-moz-opacity: 0.25;
opacity: 0.25;
}
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 2:57 pm
by Don Chambers
Hmm.. just noticed you said this happened with the upgrade from 1.4.0 to 1.4.1 - the new editor (xhina) started with 1.4.0. Did it work ok with 1.4.0?
The firebug errors you are reporting are not fatal. I think Garvin's suggestion was for you to check for javascript errors, not css errors.
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 10:05 pm
by MrLeeh
Yes before the update it worked fine. Actually I don' t get any other error messages.
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Tue Feb 17, 2009 10:23 pm
by MrLeeh
Sorry I made a mistake. Before 1.4.1 I had 1.3.1 so I guess Xinha was not installed before. Is there any reason why Xinha should not work?
I found this sourcecode for my editing window:
Code: Select all
<script type="text/javascript">
_editor_url = "/mrleeh/htmlarea/";
_editor_lang = "de";
_editor_skin = "silva";
var editorref = '';
</script>
<script type="text/javascript" src="htmlarea/XinhaCore.js"></script>
Can someone tell me where the path to the script is set in Serendipity. It seems to me that it should not be
htmlarea/XinhaCore.js but
/mrleeh/htmlarea/XinhaCore.js
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Wed Feb 18, 2009 11:02 am
by garvinhicking
Hi!
Are you able to use Firebug, open the "Net" tab and check the files listed there? It should contain XinhaCore.js, and you should check if it returns a 404 status.
Since serendipity_admin.php is called in the root of /mrleeh, the relative link htmlarea/xinhaCore.js should work.
Regards,
Garvin
Re: Upgrade to 1.4.1: Can' t use WYSIWYG Editor
Posted: Wed Feb 18, 2009 11:24 am
by MrLeeh
Thank you for the tip with Firebug. I found that some .js files couldn' t be loaded because I had no rights to read them. Everything is fine now. I changed the rights with chmod and now I can edit.
Thanks guys