WP-Blog and WordPress 3.0
During the night (CET) WordPress 3.0 saw the light of day. This is a major update to WordPress that adds a lot of new functionality along with a much improved administration backend.
I’m not going to go into details about all the changes in WordPress 3.0. You can read about the release here. Or if you want to skip directly to the juicy new features you can go here.
But what about WP-Blog?
WP-Blog works fine with WordPress 3.0. There may be minor things that needs adjustments but WordPress 3.0 does not completely break WP-Blog :)
What about the inclusion of WordPress MU into WordPress 3.0?
WP-Blog did not work with WordPress MU before because it works in a very different way. I haven’t had time to look into this in WordPress 3.0 yet but I don’t expect this to have changed. So if you want to use WP-Blog you cannot use the MU feature in WordPress 3.0.
Problems?
If you discover something that is not working properly please contact me and don’t forget to include a link to your WP-Blog page so I can take a look at your page.
WP-Blog v1.1.3
It’s time to update to WP-Blog v1.1.3. This version contains one bugfix that fixes an exception so far only seen on Snow Leopard.
I have also loosened the demo restrictions in this version. Starting with v1.1.3 WP-Blog will allow you to save and restore your customized settings in demo mode. The WordPress path will still be reset when you open a project in demo mode and publishing will be disabled after 5 minutes.
To see what is new in v1.1.3 check out the changelog.
This is a free update and requires RapidWeaver >= 3.6 and OS X >= 10.4 (Works with RapidWeaver 4).
Go grab your copy now…
WP-Blog v1.1.2
Hot on the heals of WP-Blog v1.1.1 comes v1.1.2. It contains one bugfix that fixes a problem opening pages that was saved with the demo version in the registered version.
To see what is new in v1.1.2 check out the changelog.
This is a free update and requires RapidWeaver >= 3.6 and OS X >= 10.4 (Works with RapidWeaver 4).
Go grab your copy now…
WP-Blog v1.1.1
WP-Blog v1.1.1 has just been released. It contains one bugfix that not all of you are affected by but you should still upgrade to this version.
To see what is new in v1.1.1 check out the changelog.
This is a free update and requires RapidWeaver >= 3.6 and OS X >= 10.4 (Works with RapidWeaver 4).
Go grab your copy now…
Changes to WordPress installation location
Sometime during the development of WordPress v2.8.x they started to be more strict about where WordPress has to be installed if you want the blog front-end (WP-Blog) in another directory.
Before this change it was possible to have WordPress installed completely separate to where you would like to have your WP-Blog page. But with v2.8.x WordPress has to be installed either in the same directory as WP-Blog or WordPress must be in a subfolder of your WP-Blog page. All other configurations seems to be unsupported from now on. I have listed the supported configurations here and I will put this in the documentation shortly.
Install WordPress & WP-Blog in the same folder:
/blog/ <= WordPress & WP-Blog
Install WordPress in a subdirectory of your WP-Blog page (recommended):
/blog/ <= WP-Blog
/blog/wordpress/ <= WordPress
If you use the first configuration then you will need to re-publish your WP-Blog page everytime you upgrade your WordPress installation, if the filename is “index.php”. Therefor I recommend that you use the second configuration because that is simpler to maintain. And it is also the default configuration in WP-Blog when you add a new page.
So if you are experiencing strange behaviour with your blog check how your site is setup. And if it doesn’t obey to any of these two configurations then you need to change your setup.