Finally, the WordPress Multi User Support Forum is now online but a little empty. The new release is ready and I’m hoping it’ll be live tonight but my install of Apache2, PHP and MySQL at home is playing up so it’s not tested yet. Check back later and post to the forum if you have any problems!
Tag Archives: WordPress
WordPress 1.5 is out. WPMU release to follow
WordPress 1.5 is available now from the download page!
If you’re using the last snapshot of WordPress MU then you’re using a very similar version, but I’ll have another snapshot out soon with the official 1.5 code!
Congrats to the WP developers who put so much effort into this release!
What's the GPL? WordPress and PEAR Cache Problems
Ben Ramsey explores some of the issues when you write GPLed code that uses code from the PEAR library.
I had forgotten about the differing licenses used by PEAR and WordPress. They’re unfortunately incompatible and you can’t ship PHP licensed code in a GPL project without an “exception clause” in your GPL license. A change to the license of WordPress would require the agreement of *all* copyright holders of code in the project AFAIK.
Thankfully, I don’t ship PEAR Cache with WordPress MU. I use it if it’s installed already, WPMU isn’t dependant on PEAR Cache being available to work.
I think that gets around the incompatibility. Doesn’t it?
Google "nofollow"
Well, Google’s nofollow attribute is one way of putting off comment-spammers but it won’t stop them. They’ll continue to spam in case they come across a site that doesn’t support the new attribute.
I may look at adding rel=”nofollow” to links here, but it’d be handy to have a list of “safe” URLs that are safe to link to. Perhaps a WP plugin, backend interface and db table?
In other news, the number of spams getting through to the moderation queue has dwindled down to zero (besides the edgesaver one of course!) so it’s not a problem here right now.
PEAR Output Cache and WPMU
One of those things PHP doesn’t do well is load large libraries of scripts into memory and parse them quickly. WordPress and Smarty fall firmly into this category and the caching I’ve done so far has only addressed half of this problem: cached pages don’t load any WordPress code, but the heavy Smarty library was still loaded.
I’ve now modified my code to use the PEAR Output Cache and that avoids loading the Smarty templating system. On a heavily loaded server this should make quite a difference to visitors. Things still need tweaking, I may need to introduce a “time” aspect to the cache key as pages could be cached indefinitely but for now it seems to be working really well!
Note to self, please remember that gzip compression upsets PHP’s output buffer. Note to everyone else, don’t set “gzip compression” in the backend or your blog will be foobarred! (Thanks Mel for testing his blog and reporting problems with it!)
WPMU Registration Page – alpha quality
Open this file in your browser, download and copy into your wp-inst/ folder as “wp-newblog.php”
Create the following entry in your root .htaccess file too (modify to suit your site):
RewriteRule ^([_0-9a-z-]+)/wp-newblog.php(.*) /wp-inst/wp-newblog.php [L]
Call it by going to http:// example.com/main/wp-newblog.php
It’s a very simplistic script, there’s no error checking, it creates a new directory before handing over control to the WordPress install.php
Give it a whirl but when you’re finished be sure to delete it or move it out of the way!
WordPress Multiuser Snapshot
I decided to release a new snapshot of WPMU today because of a problem posting comments. There’s also a few more changes, they’re listed below. Go download it and play!
- The referer plugin now uses PEAR Cache. This should speed up pages significantly as MySQL won’t have to lock so many reads when the table is updated!
- Kitten’s Spaminator has been upgraded to the latest version. This version has a very nice admin page to configure it without editing the plugin file itself.
- A bug in comment posting stopped them getting through, fixed.
- To speed things up, template compile checks have been turned off. If a template changes make sure you do it from the backend.
- Misc bug fixes and WP upgrades.
Later I looked into the sql errors people were having during the install and thanks to Chuck I think I figured out what happened: If you’re getting SQL errors about table names with “wp-inst” in them make sure you’re not calling setup-config.php or install.php using the urls http://example.com/wp-inst/wp-admin/setup-config.php and http://example.com/wp-inst/wp-admin/install.php
The correct urls should be http://example.com/main/wp-admin/setup-config.php and http://example.com/main/wp-admin/install.php
The “main” part of the url is handled by mod_rewrite. Follow the links in the installer and you’ll be fine!
I’m going to update the installer so it knows to replace “wp-inst” with “main” when people call the installer incorrectly.
Here are the URLs you’ll be calling when you install WPMU, the first page is a WPMU page, but the rest is bog-standard WordPress installer stuff:
Here are the links I go to on my local machine:
http://localhost/ – creates directories, page starts with text, “Welcome to WordPress MU, the Multi User Weblog System built on WordPress.
You’re probably seeing this message because you’re installing WPMU!”The link at the bottom of that page points at this page:
http://localhost/main/wp-admin/setup-config.php
This is almost the same file that exists in WordPress itself.Hit “let’s go!” at the bottom of that page to go to:
http://localhost/main/wp-admin/setup-config.php?step=1
Fill in the form there and go to:
http://localhost/main/wp-admin/setup-config.php?step=2
where you’re asked to “run the install!”That goes to
http://localhost/main/wp-admin/install.php
and clicking on “First Step” goes to
http://donncha.homelinux.net/main/wp-admin/install.php?step=1
to fill in weblog title and email address.After submitting that form I get a login link and username/password to use when logging in at http://localhost/main/wp-login.php
I also fixed the table prefix bug too, but that’s not in this release. It’ll be in the next one!
Kitten's Spaminator
I’ve just updated to the very latest version of the excellent Kitten’s Spaminator Kitten’s Spaminator so go check out the new options page to configure the plugin! It’s at Options->Spaminator.
Testing Gnome-blog and WordPress
This is a test post from Gnome-blog. Very simple interface, but I prefer the javascript/html bookmarklet myself!
Later… It works, sort of. I was able to post the above text but I couldn’t:
- Pick the category to post to
- The post title wasn’t set.
- The Smarty cache wasn’t cleared so I presume xmlrpc.php doesn’t go through the usual wp-admin/ backend.
WordPress Multiuser Jan 9th Snapshot
Here’s a major update of WPMU. Go download it now!
New in this snapshot:
- Use PEAR Function Cache if available. Several plugins have been rewritten so they’ll cache their output to save on databases processing.
- Main WordPress loop has been cached in a better way. If a page is now cached all we need to do is get a few settings from the database.
- The last release was plagued by the wp-login feature that redefined the site url if the blog was moved. As all wpmu URLs are virtual this was a big one!
- Kitten’s Spaminator will now import keywords from the “main” blog to help detect spam in other blogs. (As there’s no registration page yet you’ll have to trust me that it works great!)
- Previously when comments were posted, regardless of whether they were spam or not, the Smarty cache was cleared. This wrecked any performance gained by caching content so now the cache will be refreshed from the backend.
- Because of too-vague mod_rewrite rules, posts with titles containing 4 digits failed.
- Misc bug fixes and WP upgrades.
