Hi,

I'm implementing the new FCKeditor site with Drupal. I've checked that the current FCKeditor module is not compatible with the new Drupal 4.7. I've also noted that the module should be completely rewritten. Well... I did that job.

You will find the new module attached. I've also changed some behaviors of it and implemented a new popup system. Just the File Browser connector remained the same (I didn't test it actually).

Well... let me know your thoughts about that. I think it could be committed as the current version of the module. I would also like to be included as a developer of the module, so I can participate even more actively on it.

Just let me know your thoughts about that.

Best regards,
Frederico Caldeira Knabben
----
http://www.fckeditor.net
"Support Open Source Software"

CommentFileSizeAuthor
#17 fckeditor.module_0.patch1.96 KBhavran
fckeditor.tar.gz14.21 KBFredCK

Comments

efolia’s picture

mmm... it sure doesn't work for me. Neither the popup nor the in-window versions do anything (no menu beside the ok/cancel twins, and no way to input in the popup... the in-window version doesn't do a thing). The pop-up version displays the ...popup.html file, but nothing more. I tried it under Opera, Firefox and IE. Looks like javascript doesn't kick in (I have it enabled on all my browsers, same for popups).

efolia

FredCK’s picture

Have you followed the editor installation instructions as described in the README.txt? Remember that the module doesn't come with the FCKeditor scripts.

ontwerpwerk’s picture

I will test it the coming week, but from the looks of it it is a very practical version of the module.

I did notice however that the module you made is licensed under the LGPL licence, which is a problem for inclusion in the repositories at drupal.org

FredCK’s picture

The module itself is under the GPL. FCKeditor, which must be installed separately, is under the LGPL. The separated installation is needed (maybe?) because of the licensing differences, which doesnt bring any trouble to the end user.

Actually I think that there would be no problem on including the editor in the module too, to make its installation easier. The fact is that the LGPL gives all grants of the GPL, plus some additional things. So, there would be no incompatibility in it. There would be a problem if we would do the opposite, if I would like to distribute the module inside FCKeditor, under the LGPL, which is not the case.

Any thoughts regarding this issue are welcome, as it would make the installation process much easier (actually the module would work out of the box).

Thanks for your comments.

Best regards,
Frederico Caldeira Knabben
----
http://www.fckeditor.net
"Support Open Source Software"

fwdrupal@drupalcenter.de’s picture

Hi,

it doesn't work for me too. I've tried any possible configuration but anytime it shows an error message similar to "fckeditor.popup.html not found" - no matter what basedir is configured.

And i tried all the patches posted here before too -- nothing works.

This is really bad because i like the FCKeditor much more than the tiny one...

In my opinion (i'm not a programmer) it's a problem of telling drupal where the functional parts of this module are. I suggest the problem is that i installed drupal in a subdirectory (www.domain.com/drupal instead of www.domain.com).

Bye

FredCK’s picture

Can you attach the HTML of the form page? Maybe it could give some clues about the problem.

Thanks in advance.

scroogie’s picture

Hey, its great to have you on board Fred, you are the original author of FCKEditor, arent you? I will be happy to test your contribution today eve. Will let you know the results then. It would be great if the FCKeditor module would be actively maintained again. Maybe we could tackle some integrations later, like input filters and image integration.

FredCK’s picture

Yes, I'm the "FCK" in FCKeditor. I'm discussing with other guys about the re-launch of the FCKeditor module effort. I think we'll have wonderful results here.

scroogie’s picture

Do you have some kind of Wiki-Site or something? I would like to contribute my thoughts, at least the ideas or as contrib modules.

FredCK’s picture

Well... the editor development will have nothing to do with the module development. Let's say that these are two independent developments, but as I'm working on both, there would be some collaboration between then.

So, you will find nothing regarding the module in the editor site or the Wiki. We must use Drupal resources for the module discussions.

In the FCKeditor module page (http://drupal.org/project/fckeditor) I don't see any place for open discussions, but the "Support Forum" could be used for that (http://drupal.org/forum/18), or even the module maintainer could bring us some tools in this sense (specific forum or wiki). I think that any idea in this sense is welcome.

Best regards,
Frederico Caldeira Knabben
----
http://www.fckeditor.net
"Support Open Source Software"

fwdrupal@drupalcenter.de’s picture

Hi Fred,

thanks for your efforts!

Here some information:
WAMP-Server: Apache 1.3.37 with mod_rewrite, PHP 4.x, MySQL 3.x, Drupal 4.7.3 no extra modules
basedir of FCKEditor module set to default: //modules/fckeditor/fckeditor/ (the extra slash not a typo! even without it it won't work)

HTML-Source:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /modules/fckeditor/fckeditor.popup.html was not found on this server.<P>
<HR>
<ADDRESS>Apache/1.3.37 Server at www.domain.com Port 80</ADDRESS>
</BODY></HTML>

At that stage it doesn't produce an error message in the watchdog...

The domain name is a forwarded frame to a subdirectory on my server at home (e.g. www.domain.com points to domain.dyndns.org/drupal)

Bye

fwdrupal@drupalcenter.de’s picture

Me again.

I've tried this module with another server (www.domain2.com which is not forwarded and with drupal installation at the top directory level), changed the default basedir from //... to /... and it works at a first glance smoothly.

Maybe the problem above is my configuration of the apache (but it was fine with Drupal 4.6.x and fckeditor.module)

Bye

scroogie’s picture

@fwdrupal, If the webserver cant find /modules/fckeditor/fckeditor.popup.html then you certainly misconfigured your path. You have to use the path from the perspective of the webserver. If your domain uses simple forwarding, then the /drupal prefix is still needed for your apache (that doesnt hold for vhosts). In your case it is "/fw/modules/fckeditor/fckeditor.popup.html" (because your drupal resides in the fw dir).

scroogie’s picture

FredCK: If we want to collaborate we could create a group on groups.drupal.org for the development. For now I could probably use the issue tracker and submit it as feature requests.

ontwerpwerk’s picture

Assigned: Unassigned » ontwerpwerk

I updated the HEAD/cvs with a version that uses FredCK's method of initializing the module

Some options were also added

  • you can disable certain textareas based on their id and on the number of rows a textarea has
  • Role based editor toolbars (2 toolbars to choose from)

Feel free to test it on your 4.7 install

// ssip is not tested yet

ontwerpwerk’s picture

(you will probably have to wait a little until the CVS tarball is regenerated, the date should be somewhere near 28 august)

havran’s picture

StatusFileSize
new1.96 KB

I make some small changes for Drupal wich is installed in subdirectory - using base_path() function solve this issue. Patch attached.

ontwerpwerk’s picture

Priority: Critical » Normal

Wow, that was fast....

Please open a new issue for this kind of patches, makes it easier to track what is done
(I'll check this one tomorrow)

scroogie’s picture

What exactly are you trying to do here?

-    drupal_add_js(preg_replace('/^\//', '', $base_path) . 'fckeditor.js');
+    drupal_add_js(preg_replace('/^'.str_replace('/','\/',base_path()).'/', '', $base_path) . 'fckeditor.js');

The first seems to remove a leading slash in the $base_path but the second doesnt make sense to me.

ontwerpwerk’s picture

I think the removal of double slashes should be unneccesary, adding the base path might be an idea.
I'm not satisfied about all those path variables at the moment, so I'll try to improve on them the coming days.

FredCK’s picture

Status: Needs review » Fixed

I think we can mark this task as fixed, as it has already been committed to the CVS. Otherwise we will continue discussing about it here, and we must instead open other tasks for things already in the CVS.

Please reopen it if you fill it is not the right thing.

Anonymous’s picture

Status: Fixed » Closed (fixed)