wpmu – resources

andrea_r has posted into the WPMU forums in this thread a link to a working tool for including Flickr images in blog posts. Its a slightly modified version of the original from TanTan Noodles.

It installs easily and works pretty much straight out of the box. I did, however, come across a niggling little problem; on my write post page I was getting the following error message:

Warning: Missing argument 1 for http_request() in /usr/local/lib/php/HTTP/Request.php on line 209

Luckily I was able to track down the problem and it was an easy thing to fix. Luckily 😉

The fix is as follows:

edit file: lib.phpFlickr.php, line 74

orig: require_once “HTTP/Request.php”;
new: require_once “PEAR/HTTP/Request.php”;

Simple as that.


Curiouser and curioser someone much more eloquent than I once penned.

My TanTan Noodles Flickr plugin conundrum continued. I wasn’t able to immediately resolve the problem so decided to come back to it later; there was a post I wanted to write into that blog so I would have to do the image thing the long way around for now ; )

Curiously I then noticed that the file upload dialogue box on the write post page was filled with a view of the blog’s live page; the file upload dialogue had gone, disappeared, never to return!!

Well, not quite. I deactivated the plugin and the file upload dialogue returned. A curious feature to the plugin ; )

I’ve asked at the TanTan support forum if there’s a fix for this. I’ll mention it if this problem is resolved.

Another option to manage Flickr photos wihtin a WP (MU) blog is FAlbum

FAlbum : URL = FAlbum WP 1.5/2.0 plugin
Install instructions : FAlbum Install Instructions
Support Forum : FAlbum forum

Well respected, however “FAlbum includes the code needed to have a recent pictures or random pictures section on your sidebar” which, since I’m trying to set up a WPMU install that is as “point and click” as possible for my bloggers, means that no matter how good it is its a non-starter for this project.

I also note that FAlbum requires an entry within the .htaccess file which, although I’ve not looked into this requirement (at all) makes me less than comfortable because .htaccess problems are the bane of a WPMU install. If I can get away with making as few “customisations” as possible then there is less to break (especially on upgrades). It also means, to me, that the install is more robust.

Time has hurtled past since my last post, partly because I've been busy elsewhere and partly because I've been reading up on WPMU, oh, and I've had some quality time with the other parts of my life ; )

Since mentioning the earth-shattering discovery that there is no panacea [shock][horror] to developing a WPMU site The Outdoors Encounter have moved along a little. Principal focus at the mo' has been toward developing a usable "front end" to the domain (the sub-domains and the blogging are up and running).

One or two snippets have popped up recently;

The principal source for the functions that are called from the templates is the wpmu-functions.php file in the /wp-includes/ directory. For instance;

As samchng has recently pointed on in this thread in the WPMU forums get_most_active_blogs() does exactly as it says on the tin.

There is a useful plugin, called List All that is available from wpmudev.org that is useful and usable. List All is probably the better option because its a plugin and there's no chance that a future update of the base files is going to overwrite your hard-earned customised code.