Fly together Forever

I got married several months ago, but did not have time to put up all the photos to share with my families and friends all over the world.

Just installed Gallery 2 and WPG2 for Wordpress and all wedding photos are all uploaded. However, you do need a login/password to access them. If you know me personally, please ask me for that.

Mysql 4.1 is available in the new server from migration. The transition from 4.0 to 4.1 is quite transparent as long as I do not try to set the default encodings of the db/tables to UTF-8.

However, as the proper way is to set the encodings in mysql 4.1 correctly, I decided to do it sooner rather than later.

According to the document, if UTF-8 was saved in the mysql 4.0 db although the default encoding is not UTF-8, then:

However, you should avoid trying to convert directly from latin1 to the "real" character set. This may result in data loss. Instead, convert the column to a binary data type, and then from the binary type to a non-binary type with the desired character set. Conversion to and from binary involves no attempt at character value conversion and preserves your data intact.

As it turns out, wordpress 2.1-alpha actually just save the text as latin1 strings, so no need to convert the fields to BINARY first, setting charset to UTF-8 on those fields is sufficient.

An sql file is prepared for doing this. (Proceed at your own risk and always backup first)

I have been really busy lately, so I hadn’t noticed that FCKeditor 2.3 finaly was released a week ago until yesterday.

It seems it is now the time for a new release of SJSD which supports the latest FCKeditor: The svn trunk of SJSD supports 2.3 already, but no public release yet. I will try to make a release if I can find some time to sort it out.

In addition, a new patched EditMonkey would be nice as well, but as I haven’t ported the FCKeditor plugin for wordpress to FCKeditor 2.3 yet, it requires much more time, which I probably won’t do until some time later when I am not so occupied.

Have no clue, but since several days ago, my blog had kept having comment spams, although CaptCha! is enabled. I have no choice but to try to activate Akismet instead.

As this is a 2.1-alpha (svn) of wordpress, it refused to store the WordPress.com API key. However, after a svn up of wordpress, it got fixed.

I deactivated plugin CaptCha! and went and saw how well Akismet could do its job. So far, Akismet caught 8 spams perfectly without missing a single one. I guess I will stick with Akismet then.

I just did not come up how can the spammer bot work around the Captcha challenge…

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.

(more…)

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.

(more…)

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)

(more…)

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.

(more…)