Fly together Forever

Yesterday, I notified the author of EditMonkey about the pre tag bug patch, However, he already made his mind about dropping support of FCKeditor for EditMonkey 3.0. Although personally I prefer FCKeditor, I agree that focus on one editor is better for stability issues with only one developer working on it.

Due to working on SJSD, I am pretty familiar with FCKeditor code base. When I tried the built-in tinyMCE editor of WordPress, I noticed it supports <!–more–> and <!–nextpage–> much better than the FCKeditor does in EditMonkey 2.5: in tinyMCE, an image is displayed instead of an invisible comment.

As a big fan for PRE tags, I use it a lot in blog. Unfortunately, the WYSIWYG editor deployed in this blog, EditMonkey 2.5 does not like PRE so much: once stored in database, all the new line in the PREs are missing, which is quite annoying. Thus I prepared a fix here.

Yesterday, I upgraded the eZ publish setup in SCIM project website from 3.5 to latest stable version 3.8. For your references, here I will present the details about how to achieve this.

Before anything else, first make your eZ offline in case users want to access it. You can achieve this easily by just replace the eZ index.php with a file stating that “the site is undergoing an upgrade and will back online soon” or similar.

As for every open blog (open as in everyone can post comment without register first), anti-spam is of high priority.

Googling around for a WP plugin which implments Captcha, I found a list.

With further investigation, I decided to try out Captcha! (BTW: there is an open contest sponsored by eZ among others, in which one of the three available categories of application is captcha. However, as it turned out that it has too little information in the English post, I do not know much about this contest)

After making a patch for eZ to work with lighttpd/fastcgi, I thought it should be also possible to make eZ publish work with Apache CGI mode (I am still using apache1.3.34).

It is well known that eZ publish does not play well with CGI, thus it can not work properly with some minority web servers, such as lighttpd and nignx (and I managed to google out an English blog about how to configure nignx) which only support php in CGI mode. However after reading a thread in eZ forum, I wanted to give it a shoot.

First, I have to decid which of the two minority web server I’d like to try. Although personally I prefer the cool name of nignx (pronounced as engine X), it does not support php directly: instead it depends on lighttpd to handle php request. It is obvious I have to go with lighttpd to run eZ.

After some painful googling about howto make lighttpd work with fastcgi/php etc, I finnally managed to work out a way to get through the mess, and make eZ Publish work with CGI as smoothly as in php apache mod.

Although I am most familiar with eZ publish and have little knowledge about wordpress, but I bet the latter one is more appropriate for dedicated blog. That’s the reason this site was established based on wordpress.

However, that’s means I can not use the SJSD project.

As the first post in my blog, I am delighted to announce the availability of SJSD 0.3.1.

In case you do not know what SJSD is, here is a short description copied from its website in SF: SJSD provides a fully integrated, feature complete and extensible WYSIWYG open source online editor for eZ publish. It is implemented in the form of a FCKeditor plugin and an eZ publish extension and requires no modification to FCKeditor/eZ publish core.