Comments on: JavaScript void links in OpenCms 6.2.3 WYSIWYG

By: Sebastian

Sebastian — Tue, 14 Apr 2009 17:15:50 +0000

Hi Bryce,

sorry for commenting so late (I took a few days off). Have you resolved your issue?

best regards,
Sebastian

By: bryce

bryce — Thu, 09 Apr 2009 18:42:58 +0000

It just says “best available” for all the options listed under “preferred editors”

hmmm….

By: Sebastian

Sebastian — Thu, 09 Apr 2009 17:05:27 +0000

Hi Bryce,

just open the preferences dialog and open the editor tab. There you can set the used editor.

best regards,
Sebastian

By: Bryce

Bryce — Wed, 08 Apr 2009 19:24:28 +0000

Thanks for the reply. Yes I am running 6.2.3 and fckeditor 2.3.2. The file I edited was the one described.

Is it possible I am not using the fckeditor? I see in my modules HtmlArea WYSIWYG editor plugin and LEdit editor. How do I know which one is the primary?

Or would the change I did earlier that created the disappearance of the editor mean that its installed/loaded?

-Bryce

By: Sebastian

Sebastian — Wed, 08 Apr 2009 18:19:12 +0000

Hi Bryce,

first make sure that you are running 6.2.3.. maybe there was a difference in another version. Then maybe use bugzilla and the JS console to get a detailed error JS message.

Also check the right file. See:

Update: In OpenCms 6.2.3 the file is called fckeditorcode_gecko.js not fckeditorcode_gecko_2.js.

I’m sorry but I don’t know another solution from the top of my head.

Best regards,
Sebastian

By: Bryce

Bryce — Wed, 08 Apr 2009 16:20:24 +0000

I am running OpenCMS 6.2 and have this same issue described on this webpage. However when I change the fsckeditor JS file to the “this.EditorDocument” my fsckeditor dissappears when I select the edit function of a webpage. Is there something else I need to do?

If I revert the file back the editor appears again but obviously nothing is fixed.

Suggestions?

By: Sebastian

Sebastian — Tue, 31 Mar 2009 16:48:34 +0000

I’m glad you found the problem! These are the kinds of problems that drive me nuts! Thanks for reporting back.

By: Roman Kopac

Roman Kopac — Tue, 31 Mar 2009 15:52:54 +0000

I finally found the cause. There was another server that was rsyncing Java classes among servers in the cluster. It also rsynced resources with Javascript files.

By: Roman Kopac

Roman Kopac — Wed, 04 Feb 2009 21:18:11 +0000

You are right., OCEE is most likely not the guilty party. I will try your advice and hopefully find the component that caused this.

By: Sebastian

Sebastian — Wed, 04 Feb 2009 18:02:40 +0000

Hi Roman,

as far as I know the OCEE cluster has a dedicated workplace server so in theory(!) it is unlikely that this causes the problem (although I have had problems with clustering and the frontend). I think it is related to some server side caching.

I would recommend tracking down the problem starting at the application server. Simply do an HTTP request starting from the application server (this should not go through any proxy (hopefully)) and then look if you still get the wrong version. Then you can step back one node at a time and find out the component that’s causing the problem.

This is how I found out that the transparent HTTP proxy in a firewall component was enabled (and nobody knew it was there).