A Mind @ Play

This idea is one which keeps popping up from time to time, normally on those occasions when it would actually come in useful, only to be thrown on the backburner for another time or a more talented author. Well this time I’ve decided just to throw the idea down on electronic paper for anyone with the skills and the time to make it work have a go. Of course, it’s quite likely that such a website already exists and that I just haven’t yet been able to find it, but if anyone knows of such a place, let me know!

Ostensibly the website is aimed at those allegedly few remaining people who cook, though it would appear equally useful to people planning dinner parties, students looking for something to go with their pasta, or just about anyone curious enough to experiment with a few different ingredients. In its essence, the website would be nothing more than a large recipe repository, with everything from snacks and sandwiches to stews and casseroles, with anything in between. Recipes would be submitted by users, moderated and standardised, but the slightly clever part is that these recipes would not be displayed as flat text files—it’s 2007 after all—but would be cross-referenced in such a way as to make the whole collection completely accessible.

(more…)

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.

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.

This certainly isn’t my area of expertise, but I’ve been trying to figure out a way to integrate the Language Switcher plugin with a widget-enabled theme. As this hasn’t yet been implemented, I copied wrote the simplest of Widgets which will list the available languages on your blog in the sidebar.

There really isn’t anything special here, but for people even more hesitant with code than I am, pop this file into the wp-content/plugins/ folder of your WordPress installation, and then enable it via the Plugins admin page. You should then find the Widget available in the Presentation -> Sidebar Widgets admin page. At the moment, the Widget will display your available languages listed only by name. I’m still learning how to allow this to be changed from within the Sidebar Widgets page.

Click here to download Language Switcher Widget v1.0.

Happily, one of the best things about the Mozilla Foundation’s flagship browser Firefox, is the sheer breadth of additional functionality provided by an active development community in the form of addons or plugins. There’s a great range in terms of ease-of-use, function and stability, some which are so useful as to almost warrant standard inclusion, others merely worth playing with from time to time. It should be noted of course that adding plugins can cause problems with Firefox’s stability and security, though many of those listed are fairly mature projects and should not pose much of a risk. Here are a few I’ve dabbled with from time to time:

Adblock or Adblock Plus - There’s fair advertising, and then there’s frankly unreasonable advertising. I can see the merits of allowing sites to earn funding through the placement of adverts related to their products, whether they come from Google or elsewhere, but some web adverts go too far. The popup plague of yesteryear might have been largely beaten back, but that doesn’t prevent wiley coders from placing wholly obtrusive flash adverts in every nook they can find. Unfortunately their actions can only serve to give web advertising a bad reputation, and drive people to finding ways of blocking adverts wholesale, obtrusive or otherwise. Of course there will always be a small minority of web users who cannot stand to see web adverts in any form, but for their purposes, and the folks seeking refuge from the advertising bombardment, Adblock/Adblock Plus will fulfil their every need.

To tell the truth, the history of these two projects confuses me, save to say that at one time or another one or both of these plugins has been under development. As I understand the current situation, Adblock Plus is the more highly recommended, as it’s more heavily featured, comes with some default filters to subscribe to which can get rid of most adverts with the minimum of fuss for the end user, and has a much reduced resource footprint to boot (pardon the pun).
(more…)

Another site for those lovers of audiobooks. Podiobooks offers a way for authors to showcase their talent for free, parcelling up their work into episodes which can be delivered via podcast or downloaded manually from the website. Whilst listening to the books is free, the website recommends users to donate, as 75% of donations goes straight to the authors themselves, which they regard as a much more equitable way for authors to market their abilities. It also offers something of a return to the serialisation of novels so popular in the past; subscribe to the book(s) of your choice via RSS and listen to the podcast via your favourite media player, or upload to an mp3 player to listen on the move.

As I found recently, if you’re planning on moving your WordPress blog around on your server or domain there are a few things to be aware of. Most importantly, do not move the blog before setting up the WordPress for the new location!

1. Go to the admin section of your blog, select and find the Options > General panel.
2. Change the WordPress address and Blog address entries to reflect the new location of your blog.
3. Update your blog, and do not worry if there appear to be problems, simply log out.
4. Delete the wp-content/cache folder from your WordPress installation (if it exists).
5. Move the WordPress files to their new location, including all subdirectories.
6. If you use Permalinks, update them via the Options > Permalinks panel.
7. Update the settings for any plugins which require addresses which have changed.
8. Navigate to your new blog address and check everything is working.

Whilst this should update most of your settings to reflect the blog’s new location, some problems might arise with links and images, particularly relative links if you have changed the blog’s location within a single domain. If this is the case it would be easiest to edit the links en mass via the SQL database, however if this affects only a small number of posts it could prove simpler to edit these manually.

Note: WPG2 users might find the WPG2 Plugin page on their WordPress page reports everything successful, yet their embedded gallery page attempts to find images under the old structure. In this case, Show/Hide Manual Configuration Form will display the entries which need manually updating to reflect the blog’s new location.