FCKeditor: link to fckdialog.html wrong

That's probably easy to fix, but I need to know the configuration setting that needs to be set. There is no such setting defined at all currently, so it seems that FCKeditor is using a wrong path by default.

Could you look for a documentation page or example code snippet for this setting?

Heh. That is what I would call "Oops." ;)

Hello !

+1

Did you solved the problem ?

Samuel

France.

No, even after hours of debugging I was unable to define FCKeditor's editorBasePath configuration setting in a way that it correctly uses the proper path. This needs someone to step up and debug what exactly goes wrong, and when and how we need to define the base path.

This is a patch to FCKEditor 2.6.3 that solves this issue without using any patch provided here. It seems works, don't know if it's the better solution.

Altering/manipulating the editor library won't fix. This must be caused by something else, since the FCKeditor module does not have this issue.

Confirmed: if I pull up the and of the demo's in the _sample directory it works fine. But using wysiwyg it fails.

The problem is that BasePath is the name of a property of FCKConfig object and FCKeditor class... and it points into two different locations (yup, it's confusing).
In FCKeditor class, it is a path to wysiwyg/fckeditor, while in FCKConfig object it is a path to wysiwyg/fckeditor/editor.

In short, what do we really need to set in the $init array, is FCKConfig.EditorPath, because FCKeditor.BasePath equals FCKConfig.EditorPath.

And here goes a patch for DRUPAL--5 branch

Wow - that's indeed totally confusing.

Tested the patch, works - committed to all branches.

Thanks!

I'm sorry to all those providing the fix, but I don't understand how to use it. If someone could help walk me through how to solve this issue I'd be very grateful and the project would gain another donation.

Thanks.

The only other issue that holds off a new release is #364782: Stylesheet of sub-themes not loaded - I just need a confirmation on that patch to create a new stable release (which means you do not have to apply this patch). If you cannot wait for this, see http://drupal.org/patch/apply - that said, the changes in this patch are so minimal that you could apply them manually.

Hi all!

Funny, this is my first time trying to get WYSIWYG API and FCKeditor working and man was I glad to find this thread and to find out that others are having the same problem and that a fix is on the way.

I don't have any experience applying patches in this context. I don't have command line access to the server so can someone help me with some tips on manually applying the patch, please?

Thanks, in advance. . .

BTW, I kinda need this to be working by tomorrow morning (Sat morning GMT).
I'll survive without it but I really want the relevant folks to be able to see how image placement is done and tomorrow is training day.

Silly me. You can simply download the latest development snapshot of Wysiwyg API, which contains this fix.

Thanks,

I did check the release notes for the dev snapshot to see if the issue had been addressed but all it said was "Development snapshot for 6.x." which didn't help me much.

Sorry for bugging y'all. . .

BTW, I worked out how to read the patch file and manually patched the module.
Afterwards the editor started acting strange.
Rather than replacing the textarea with FCKeditor and the content to be edited it filled the textarea with the full content of the page (node, menus, everything) I was hoping to edit with FCKeditor. . .

I'll let you know if the latest dev version sorts me out. . .

Yes, again, simply use the latest development snapshot that can be downloaded from the project page.

Hi,

I'm glad too that someone else experiences this problem. I'm new to Drupal and I kept on blaming my own noobiness. Anyways. I've downloaded 6.x-2.x-dev of Wysiwyg, but it does weird things: duplicates the original window inside the editing box. What to do? Maybe I should move to a different texteditor ...

yours always,

Erik

Please ensure that your browser does not load out-dated JavaScripts first. If you did ensure that, then please either open a separate issue, or better yet, join #drupal-wysiwyg in IRC (irc.freenode.net).