random thoughts to oil the mind

Tag: WordPress Page 2 of 3

Relying on Plugins


Plugins can be a major boon. They can add variety to a site, integrate third party software, collect feedback, improve navigation, or add features. Occasionally they may become integral to the way a blog is run. But they can also become a burden or a major stumbling point. The recent WordPress 2.5 release made a large of plugins for the software incompatible, and outright broke a few. In those cases where plugins simply provide some added extraneous functionality, such breakages might not be a problem, but where they form an integral part of a blog the potential changes can bring a site to a halt.

Yet some downtime during a WordPress update is not the only worry when it comes to plugins. Whilst major updates often accentuate the problems, there is no guarantee that plugin authors will continue their work to cope with bugs and software changes. The small WPPA plugin currently used on this blog was recently broken by the WordPress update, but the author considered that the features introduced in the recent version might make his plugin obsolete, and only touched up the plugin to work with 2.5 (so far). Since I hardly post any photographs, such a change makes little difference to this site, but for many others migrating to another plugin could prove a major job if automated tools aren’t available. Others may have experienced such changes when moving between multilingual plugins as the features and support changed, from Language Picker, through Polyglot, to Language Switcher or WP_Multilingual. Such a migration might involve moving media around, altering themes, or having to change tags or syntax within WordPress posts.

How do you approach using plugins on WordPress? Do you consider WordPress should avoid leave extra features to the plugin authors rather than implementing features already well covered (e.g. tags, photos)? Should plugin authors attempt to implement migration tools or leave it to end-users to do the necessary conversions?

Another Day, Another Plugin

WordPress Plugins

With the news that WordPress Photo Album plugin potentially contains a security vulnerability, I decided it was probably time that I took stock of my increasingly long plugins list and removed some of the outdated and superfluous items. One of the greatest improvements to WordPress of late has been the automatic update checks provided for plugins listed on the official site, which whilst by no means universal does at least mean that updates for many popular plugins will automatically be reported without the need to check up on each one manually. This little list of what remains represents some of the better plugins I’ve encountered.

To Blog, or Not to Blog


That is the question; as the well known soliloquy roughly goes. A Mind @ Play is now a year old, and not a day wiser, as far its author is concerned. Courtesy of GeneralStats, I can see that in the past year (excluding this post) there’ve been 57 posts, 18 comments/trackbacks, together a total of 31,400 words, and over 8,000 spam comments caught by Akismet. But to what end?

This isn’t intended to be another one of those ‘blogging about blogging’ posts, but occasionally one has to ask why we blog at all. I wouldn’t claim to be anything near an expert on the subject, but it would appear that the more successful blogs do just that: ‘blog about blogging’. Nor should that sound derogatory, some of them do an exceedingly good job of it, but there are only so many times you can read the ‘top 10 ways to get more readers’ et al. But then these people tend to come from the professional end of the blogging community, those who aim to earn something through their work. There were and are no such intentions with this blog, and if there are any advertisements on this site I can only say they are unintentional.

WordPress 2.2 Database Character Sets

For those upgrading their WordPress powered blogs to 2.2, just a word of warning regarding the new character encoding options available in the wp-config.php file.

The standard file should have a section which reads:

// ** MySQL settings ** //
define('DB_NAME', dbname// The name of the database
define('DB_USER', 'dbuser'); // Your MySQL username
define('DB_PASSWORD', 'dbpassword'); // ...and password
define('DB_HOST', 'localhost');
define('WP_HOME', 'http://www.yourblog.com/');
define('WP_SITEURL', 'http://www.yourblog.com/');
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', 'utf8');

Note the new options added at the bottom regarding the codepage used in the blog’s database. If these are set incorrectly they may make your blog unreadable, else prevent special characters from appearing correctly. I personally found that commenting these two lines out left the blog functioning as before, but for people wishing to change the codepage of their database, WordPress has a rough guide available, originally written for the beta testers.

Language Switcher Widget v1.01

After a little more research and experimentation, I’ve updated the little Language Switcher widget to enable the user to choose whether to display flags and/or names for the available languages when setting up the widget, and change the heading in the sidebar if required.

Click here to download Language Switcher Widget v1.01.

Page 2 of 3

Powered by WordPress & Theme by Anders Norén