• Only Administrators see the config page
• Fix the compatibility problem in 2.3

Thanks to Firebug, this new fix gets rid of the CSS-Hack, directly fix on the js file, and work better with IE7.

It’s basically for some unknown reason, the oContainer is not empty when calling setContainerContent(). The fix is explicitly call removeContainerContent() in setContainerContent(), avoid the double tooltip problem in Firefox:

var oOutputNode = document.importNode(oXMLDoc.documentElement, true);
removeContainerContent(); //add this line
var oChild = oOutputNode.firstChild;

Download the new fixed package.

This also contains the previous fix for wordpress <ins> <del> time parsing problem, plus simple CSS opacity fix for IE(no round-corner support though)

FancyTooltips is released in MIT License.

1. Some of your friends doesn’t check web pages everyday, and don’t even know what is rss.
2. You want you blog to be read by your friends more, but you don’t want to push them to read your entry everytime when you make a new one.
3. Live Messenger will show a flower before the contact list when someone has updated his space, and you think that is a good non-aggressive way to advertise your blog.
4. But you think Live Space sucks and you’re using wordpress.

If you match these conditions above, then Live Space Sync plug-in is perfectly for you.

Live Sync is a plug-in that allows you to synchronized WordPress post to Live Spaces, facilitating MetaWeblog API.

It was based on MSN Sync plug-in and original version of MSN Sync was created by William. The author hadn’t continue developing it so I modified it to complete the functions.

Download and Description.

Known issue: clear text would still be post on Live Space even with password-protected.

That’s basically because SK2 intercepts some actions, WP-Cache will not get notified.

I create a small plug-in for SK2, that will directly call wp-cache to flush cache, after a comment is approved.

Download this zip, extract and drop the php into sk2_plugins directory, it should just work.

Note:

1. wp-cache 2.1.0 is out, please install 2.1.0 and delete old cache before you complain this compatibility plug-in is not working.
2. Turn off ‘encrypted payload’ check in sk2, see the reason updated below.

Updated: There’s a problem discovered by Reiner), sk2 generates some dynamic hidden field to check if the page is really loaded by a browser before the comment is posted.

The ‘encrypted payload’ plug-in will cause the biggest problem, since it contains an ‘ip’ field that generated base upon client’s ip.

With wp-cache, encrypted payload will be fixed, so the ip will not match the real commenter’s ip. IP mismatch will cause a minus 2.5 karma, which will prevent many normal comments comes in.

I love linebreaks, and wordpress dev-team hates linebreaks.

When switching from ‘Visual’ to ‘Code’, or when saving, seems wordpress automatically remove simple <p> and <br /> tags…. Maybe for autop friendly and makes the post smaller…perfectly reasonable.

But when you press some shift-enter(generate <br /> in TinyMCE) in Visual, then switch to Code, <br /> will become linebreaks. Then you switch back to Visual, now TinyMCE strip the linebreaks. Without switching, yes, you can save linebreaks correctly, but if you load that article again in the editor, linebreaks will be eaten again by TinyMCE.

And worse thing is, now the post filter doesn’t generate <br /> against linebreaks
Even if I turn off the RTE and manually add 100 <br /> tags, the post filter will eat them all!!

GREAT JOB…I’m starting to feel sorry for upgrade to 2.1….

In recent update, it adds cache function so it will reduce db access and processing a lot.

However for utf-8 users, we’re running into two problems, first is the php wordwrap function is not utf-8 aware, and will be cut incorrectly. Second is that in wordpress, update_option() will not save serialized broken utf8 values correctly, so the cache function will not work at all without utf8_wordwrap() on a CJK blog.

I’ve done quick fixes on these problem:

1. using utf8_wordwrap() from php.net, to replace wordwrap().
2. do base64_encode() before saving the cache to avoid escaping problem.

Here is the fixed file, you can grab if you need to use it in utf8 environment.

Updated: Sorry the conclusion is too quick, the cache problem is also cause by wordwrap(), with broken characters, the option will not be correctly saved into database. So with utf8_wordwrap() we don’t need base64_encode(). You just need one of them to allow cache to work in Chinese environment. The file is updated to latest version 1.5.1 with utf8_wordwrap()

For example, if you use one-click upgrading MediaWiki 1.6.x to 1.7.x, you’ll see problems if you don’t run MediaWiki config again. And if you use the one-click install to install WordPress, it doesn’t work well with utf-8. Here’s a mini how-to to let you install wordpress and use utf-8 properly on dreamhost.

1. Go to Goodies-> One-Click Installs under Dreamhost Control Panel, choose WordPress. Fill-in all necessary information(url, database name, host, username, password) then click “Install it for me now” button (picture1).
2. Don’t rush to your blog url yet, go Goodies-> Manage MySQL first (you might see the new db doesn’t have a host name, but don’t add host or there might be unexpected errors. Just wait ten minutes, sometimes longer, and check again, wait until the host name you set comes up), then click phpmyadmin. (picutre2)
   When it prompts, input the database username/password you just set, entering phpmyadmin interface, select you db (picture3), and choose operation in the right frame. I wonder why dreamhost prefer Swedish, but anyway, we need to set collation to utf_general_ci. (picture4).
3. Finally, edit /wp-includes/wp-db.php. Insert mysql_query("SET NAMES 'UTF8'"); before $this->select($dbname); (line #56 in 2.0.4), then it’s done. Now you can goto your blog url and finish install. And don’t forget to fix wp-db.php again when you upgrade your wordpress.

And now you can use utf-8 correctly on you blog.

Additional Information: If you install your blog before setting the collation, you can still fix the problem, but you’ll need to set collation to utf-8 in each table, since the tables are already created with Swedish collation.

It’s a great script, but still has two nasty problem, I don’t have solution until last week.

First problem is, with Firefox 1.5+, for some reason it show double, even triple tooltips(picture). Actually someone already wrote an work around(go his site to see the effect). Just add following two lines in fancytooltips.css:

div.fancytooltip > p {display:none;}
div.fancytooltip > p:first-child {display:block}

It doesn’t solve the bug in program, just hide all node, and only show first node. However I don’t like it too much, since without the link footnote, FancyTooltips looks less fancy. I hope to select the second child also, but seems difficult–since firefox 1.5 doesn’t support too complicated CSS3 selectors like nth-child.

But then I see though it can’t do second-child, we can use last-child.

If we add an additional line:
div.fancytooltip > p {display:none;}
div.fancytooltip > p:first-child {display:block}
div.fancytooltip > p:last-child {display:block}

Now it works just fine, without changing the look of FancyTooltips.

But please note that “last-child” is still a CSS 3 selector. So the third line may not work on certain browser, and will have the same result as the original fix.(However I don’t worry too much since in IE and Firefox 1.5 it works fine. Even with unsupported browsers, it won’t break too much.Seems IE7 now have this problem.)

The second problem for FancyTooltips is, it doesn’t parse timezone part of datetime attribute of <ins> <del> tags, it always create the time as localtime, and it will be mostly wrong unless you live in the same timezone.

It will be great effort to parse all valid datetime formats, so I decided to be lazy. In wordpress, del and ins button will create datetime attribute in GMT, regardless you blog timezone setting, so we can just build datetime in GMT, everything will be fine.

Modifying the line
oDate = new Date(nYear, nMonth, nDay, nHours, nMinutes, nSeconds);
into
oDate = new Date(Date.UTC(nYear, nMonth, nDay, nHours, nMinutes, nSeconds));
will do the trick.

Now I can continue to use FancyTooltips happily

(You can apply the patch your self or just Download the modified FancyTooltips plug-in.)

Note: FancyTooltips is released in MIT license.

The plan is, to write some web developments and other programming stuff here in english, to communicate more to the world than in chinese.(also, practice my poor english)

Maybe I’ll translate several entries on my original Chinese site first