Archive for October, 2006

Oct 11 2006

Going Digital

Published by under Technology

I’ve finally made the leap and have signed up for ADSL. Friends have been saying I should do it for ages now and I am a software engineer and would find broadband incredibly useful. In fact, I haven’t had internet at home since I moved out of my parents back in April.

After consulting, what I consider to be, wise techie people, I have gone with Cable & Wireless. Whilst Newtels offering is cheaper I have heard that its service is not as reliable as C&W, and as I intent to be serving content from my home I would prefer reliability over price.

I’m still unsure as to what OS I’m going to be running on my little server box. It may be Windows to allow me to play with .Net a lot easier, or I may go the *nix route and try and get mod_mono running on it… I could even invest in a Mac Mini!!!! If only it came with a TV tuner and PVR software.

2 responses so far

Oct 03 2006

The Future of Uninstalling GG_Translate

Published by under GG_Translate

Having written a couple of plugins for wordpress, most notibly GG_Translate, I’m starting to get annoyed by some of the features WordPress provides for us plugin writers.

Firstly, I want my plugin to register its default options in wordpress when it’s activated and remove the settings when it’s deactivated. For this purpose, I assume, the wordpress devs have provided activate_[plugin name] and deactivate_[plugin name] action hooks, so I can have my functions executed when these actions happen. The downside is that in order to attach to these hooks I need to use the full folder and file name of the plugin, so for using them with the GG_Translate plugin I need to do the following:

add_action('deactivate_GG_Translate/GG_Translate.php', array('GG_Translate_Admin', 'deactivate'));

Now you may think that this really isn’t a major issue, but what happens if the person installing the plugin decides that they don’t want to put my plugin in a folder called GG_Translate, i that case I then need to start figuring out what folder they have put my plugin in… if in fact they have put it in a folder! Come on guy’s you must be able to think of a better solution.

Surely the fact that each plugin must be uniquely named means that they should be able to use the plugin name, e.g.:

add_action('deactivate_GG_Translate', array('GG_Translate_Admin', 'deactivate'));

Next up, wordpress has a really nice interface for viewing and editing all settings saved by wordpress and installed plugins ( This interface however only allows for the viewing of settings and doesn’t provide for the deletion of settings. If I want to delete a setting that an untidy plugin has created then I have to either write a quick-and-dirty plugin for the purpose of removing the setting, or I need to dive into the database and delete it by hand… not very user-friendly if you ask me.

Another thing, whilst digging around in the core wordpress code I noticed some inconsistencies. It seems entirely random as to whether or not data being sent to the database will be escaped before hitting the database. It seems too easy for a plugin developer to send a string to the database that could wipe the database clean. I think wordpress needs a much more uniform approach to database access.

Finally, its about time that wordpress started taking advantage of the object oriented features provided by PHP. I’ll give them their due, they are working on it but I’d rather they were working quicker. I also can’t wait for PHP6 to come out (although thats still way over the horizon) as hopefully the namespaces will sort out all the plugin function naming headaches. Although, I’m not about to hold my breath for either of these.

No responses yet

Oct 02 2006

GG_Translate Now With Auto-Update

Published by under GG_Translate

I’ve just posted a new version of GG_Translate in my download section (0.2.27). Those of you that have downloaded the latest version of the weekend will already have a preview as to whats new in this version. This update adds auto-updating of the plugin as soon as I put a new version online. This is, however, a very beta if not alpha version of the auto-updater.

Please note that in order to use the auto-updater your web-server must be allowed to use the fopen in php to open files on remote servers. If you’re not sure whether it does or not then either just try the plugin and if it doesn’t work revert back to an older version, or you can give me a shout and I’ll help you out.

As always the latest version is available on my downloads page.

I’m also going to write up the instructions as to how to create an auto-updating plugin. I also want to make it so that it is an intelligent auto-updater that doesn’t need to download all the plugin files for each update but only those that have changed.

4 responses so far