Wordpress

I just released WP Mollom 0.7.1. Here’s the changelog:

• fixed: all plugin panels are now shown in the new WP 2.7 administration interface menu
• fixed: non-western character sets are now handled properly in the captcha form
• fixed: handles threaded comments properly
• fixed: multiple records in the manage module not correctly processed
• improved: extra – non standard – fields added to the comment form don’t get dropped
• improved: revamped the administration panel
• improved: various smaller code improvements
• added: the plugin is now compatible with the new plugin uninstall features in WordPress 2.7
• added: the ‘quality’ of ‘spaminess’ of a comment is now logged and shown as an extra indicator

Wishing all the best in 2009!

Yes. WordPress 2.7 is out. Your favorite blogging tool has gotten a serious overhaul: a totally new administration panel, loads of bugfixes and lots of new features.

The plugin API has been extended: you should now use a seperate file to store all uninstallation logic instead of relying on the deactivate callback, options should be registered with WP (mandatory in near future versions) and the submenu structure onto which you can hook your own settings is revamped.

Translating WordPress has always been very easy through gettext and tools like poedit. The availability of a whole range of languages and dialects that can be used to replace the standard English messages in WordPress is one of the factors that has contributed to the success of the CMS.

Of course, this support for translation is also available for plugins and themes. Since language shouldn’t be a barrier, I’ve been building support for translations into WP Mollom over the past weeks. The idea is that one can download a translation libary (a .mo file with all the translated strings in his language) and install it without a hussle.

• Jon Burgerman – pens are my friends – coooool!
• YouTube – Sarah Palin, Tina Fey on SNL – I can see Russia from my house!
• CSS Systems –
• QuirksMode – for all your browser quirks –
• 6 Tips for Localizing Your WordPress Plugin · Pressed Words –
• Top 5 Free Linux Games –
• Groundhopping – A pictorial documentation of Belgian football grounds
• YouTube – A day in the life of a Portal Turret –
• YouTube – Portal Turret-Speak –
• 23 awesome license plates for computer geeks –
• Penny Arcade! – The Origin Of The CD-Keys, Part Two –
• Dear United States, we apologize for the following items. Love, Canada – A truly Canadian apology for all the “wrongs” they have done towards the U.S

Welja, ik ben natuurlijk nieuwsgierig naar de mate waarin mijn plugin wordt geïnstalleerd en opgepikt. En natuurlijk durf ik dan al eens rond te googlen. Dus gooide ik even wp-mollom als trefwoord door Google.

Wat mij opviel in het lijstje was dit:

Inderdaad, een open directory bij Clopin. Blijkbaar heeft Clopin niet alleen de plugin op zijn blog gegooid, maar ineens de volledige wp-mollom/ folder inclusief screenshots. Via die toegang is het een koud kunstje om zijn plugins/ folder uit te lezen. En uit die informatie kan ik meteen een aantal dingen afleiden.

I just tagged version 0.6.1 of WP Mollom in the WordPress Extend repository. Which means in a few moments, you’ll be able to download the latest installment of my plugin.

So, what has changed? Well, this is a bugfix release which means no new features. Here’s the changelog:

• Fixed: division by 0 error on line 317
• Fixed: if ‘unsure’ but captcha was filled in correctly, HTML attributes in comment content would sometimes be eaten by kses
• Improved: the mollom function got an overhaul to reflect the september 15 version of the Mollom API documentation
• Changed: mollom statistics are now hooked in edit-comments.php instead of plugins.php
• Added: _mollom_retrieve_server_list() function now handles all getServerList calls

Although almost all basic functions are up and running now, there’s still a long road ahead. Today, I’m happy with what I’ve accomplished technically so far, but such things as usability, performance, flexibility,… still need more work. For instance, there’s still no WordPress MU version, i8n support is still missing, the backend needs more simplifying and much more.

• Mijn Drupal workflow: enkele tips voor het opzetten van een Drupal site – Sken.be over zijn Drupal werkwijze
• SitePen Blog » Supercharge Your MAMP Environment –
• Enable TinyMCE for editing CCK text fields | drupal.org –
• 5 reasons to avoid iPhone 3G –
• PitsLamp — Fotografie & webdesign – Collega Filip Bunkens gaat zelfstandig!
• WordPress Plugin Repository – A better search through Google against the WordPress Plugin Repository

Voor zij die allerlei problemen hebben met inloggen na de upgrade naar WordPress 2.6: gewoon je cookiecache – of de specifiek cookies van WordPress – in je browser ledigen. En dan nog eens proberen om opnieuw in te loggen.

Wat is nu de oorzaak van dit probleem? Ryan Boren’s artikel SSL and Cookies in WordPress 2.6 legt het mooi uit. De beveiliging van het adminpaneel is in 2.6 verder opgedreven. Naast klassieke HTTP laat WordPress nu ook toe om te werken via HTTPS (HTTP over SSL) wat een stuk veiliger is. Technische details daar gelaten, liet WordPress vroeger 1 cookie achter die aangaf of je ingelogd was of niet. In de nieuwe versie ligt het anders: nu worden er 3 cookies gebruikt waarmee WordPress nagaat of je bent ingelogd en al dan niet gemachtigd om het adminpaneel te gebruiken.

It took me the better part of June to prepare a new version of Mollom. But today I released version 0.5.0. You can download the package here.

So, a lot has changed since version 0.4.0…

• I rewrote the SQL after this suggestion on Pressed Words. Mollom now uses it’s own table to store all it’s data instead of fumbling with the WordPress data model.
• I fixed the incompatibility issues with WordPress OpenID plugin.
• Improved the error handling.
• Status messages are now a lot more verbose
• Added the mollom_moderate_comment($comment_id) tag for use in templates and themes. This allows direct moderation of a comment without first having to go to the dashboard.
• … a lot more!

So download, go forth and protect your blog against those vile spammers through Mollom!

These two weren’t the best friends over the past couple of weeks. Since someone notified me they weren’t compatible, it took some time to figure out what was going wrong. My initial suspects was an icky way of dealing with the action hooks. Either by my plugin or WP OpenID. But after extensive testing, I concluded that the order in which the action hooks call the different plugin functions, wasn’t problem.