Does http://www.fckeditor.net/demo and http://www.fckeditor.net/nightly/fckedi ... fault.html really fail for you, or are you using an old version (or haven't cleared your cache) ?

alfonsoml wrote:Does http://www.fckeditor.net/demo and http://www.fckeditor.net/nightly/fckedi ... fault.html really fail for you, or are you using an old version (or haven't cleared your cache) ?

I tried using the demo editor here (good idea!) with FF3 and didn't seem to have a problem. There might be one difference though. I'm seeing the issue after the data is actually submitted from the editor. I'm not a developer, but I'll try to explain in more detail what I'm seeing - perhaps the others in this thread can compare the results. I'm using an older version of the editor, but I honestly don't know how to find the version number. The developers that coded my site did not include the "about" button in the editor. The first post in this thread indicates that they had already upgraded to the latest version of the editor, so my thought was that the problem might be something else.

In FF3, when I click on the "insert link" button, I have normal operation. The link window opens and I'm able to enter a link. When I click on the "OK" button in that window, it appears that the link has been created. However, clicking OK does not close the "insert link" window - when using FF3. It does when using FF2 or IE. So, it's almost like the browser is still focused on the "insert link" window. After submitting the data to my site and looking at it, the link resolves to that shown in the first post here ("javascript:void(0);/*1216036103192*/") instead of the intended URL.

I don't believe there is a browser cache issue because I uninstalled FF3, replaced it with FF2, and then reinstalled FF3 - still having the same issue. Users of my site are now experiencing the same issue and when I contact them they are all using FF3.

Hope this helps.

JayG wrote:

alfonsoml wrote:Does http://www.fckeditor.net/demo and http://www.fckeditor.net/nightly/fckedi ... fault.html really fail for you, or are you using an old version (or haven't cleared your cache) ?

I tried using the demo editor here (good idea!) with FF3 and didn't seem to have a problem. There might be one difference though. I'm seeing the issue after the data is actually submitted from the editor. I'm not a developer, but I'll try to explain in more detail what I'm seeing - perhaps the others in this thread can compare the results. I'm using an older version of the editor, but I honestly don't know how to find the version number. The developers that coded my site did not include the "about" button in the editor. The first post in this thread indicates that they had already upgraded to the latest version of the editor, so my thought was that the problem might be something else.

Don't trust the first post. This is a problem that was fixed some time ago, and his problem is that he is using cached files surely.
You must upgrade your version and then the problem will go away.

alfonsoml wrote:

JayG wrote:

alfonsoml wrote:Does http://www.fckeditor.net/demo and http://www.fckeditor.net/nightly/fckedi ... fault.html really fail for you, or are you using an old version (or haven't cleared your cache) ?

I tried using the demo editor here (good idea!) with FF3 and didn't seem to have a problem. There might be one difference though. I'm seeing the issue after the data is actually submitted from the editor. I'm not a developer, but I'll try to explain in more detail what I'm seeing - perhaps the others in this thread can compare the results. I'm using an older version of the editor, but I honestly don't know how to find the version number. The developers that coded my site did not include the "about" button in the editor. The first post in this thread indicates that they had already upgraded to the latest version of the editor, so my thought was that the problem might be something else.

Don't trust the first post. This is a problem that was fixed some time ago, and his problem is that he is using cached files surely.
You must upgrade your version and then the problem will go away.

Thanks for your help! I'll give that a try and report back here with the results.