See for a start.

I envision it as an option in the configuration that is enable when the CKFinder files are found. Checking the checkbox would then enable it for FCKEditor.

This might need to be its own module, similar to how IMCE works.


#17 fckeditor_2.patch.txt2.2 KBllc2w
#15 fckeditor.patch.txt2.06 KBllc2w


Assigned:Unassigned» wwalc

This is something that I'm already working on.
I just need more time to work on this... :-)

Yes please!

For now there is this:
but I haven't tried it yet.

Version:5.x-2.x-dev» 6.x-1.x-dev


Any progress/news on this?

Any updates on this?

The necessary architectural updates are being done at this moment.


Any updates on this?

Hi Wiktor & Jorrit, have you done any more work on this request?

Just in case anybody needs to implement this manually, I have posted a followup in this thread at the FCKeditor site describing the necessary steps...

Component:Code» File browser support

Unfortunately, this will not make it into 6.x-1.x. I am rescheduling it to a later version.

Version:6.x-1.x-dev» 6.x-2.x-dev

Why not dropping this module and move to wysiwyg? Do not waste time...

That might be a possible direction, but dropping this module straight away would not be nice to the current users. The current development lines will at least be continued to a stable version.

Version:6.x-2.x-dev» master
Status:Active» Postponed

Postponed to after 2.0. Perhaps in the CKeditor module.

new2.06 KB

I need this, so I wrote a patch. Notes --

* Patch should apply cleanly to fckeditor.module, 6.x-1.4
* Drop the ckfinder folder into the fckeditor _module_ directory, not the contrib editor directory.
* Configure ckfinder's config.php according to the notes in the file.
* Select 'CKFinder' from the 'File Browser' select box in the 'Upload Settings' configuration option.

What could be improved --

* Could design an admin menu to configure ckfinder (instead of using config.php).
* Don't think I needed to `require ckfinder.php` within the module, but do anyway.

I would be very grateful if this patch is committed (or adapted such that the functionality is maintained). I hate having to maintain local patchsets :(


Could you apply it to the 2.x branch as well?

new2.2 KB

The attached patch should apply and function on the 2.x branch (or at least, the latest tarball'd snapshot).

Status:Postponed» Needs review

Setting to "needs review" for some more visibility -- patch supplied in >>17 still applies cleanly to the current tarball but was never committed. I don't want to maintain a local patchset ;_;

Status:Needs review» Fixed

Committed to CVS, it will be in 6.x-2.2.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.