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.
WP-Blog v1.1 is here
It is finally time for a new version of WP-Blog that not only focuses on bugfixes. This time I have added a few interresting features too.
I also got a bunch of good feedback from my beta testers so this version contains a bunch of vital bugfixes too so even if you are not interrested in the new features you should grab this update.
Small status update for WP-Blog
It’s still summer but i’m back from my vacation now and i’m currently preparing the next release of WP-Blog. This will be a major update featurewise that will satisfy many of the requests I have received since the first release. Until then i’m going to share with you a couple of known issues with the current version v1.0.2 that I hope to be able to adress in v1.1.
Known issues:
- The URL in the ”base href” tag is incorrect for users with RapidWeaver >= v4.2 due to an API change. This causes some RapidWeaver generated links to become incorrect.
- The sidebar feed links all points to the main feed for some users, i.e. the comments feed points to the rss feed.
- WP-Touch cannot switch to ”normal” mode anymore. It still works fine in ”mobile” mode, as you can see on this blog.
- The automatic calculation of the relative path to WordPress from the WP-Blog page can sometimes generate an incorrect relative path.
The issues are listed in order of severity. Some may disagree on that but my main focus is to fix the ”core” functionality.
Summer vacation
It’s time for the summer holiday starting today during the next two weeks. This means that I will not be able to handle support issues as quckly as I normally do.
If you have urgent issues getting one of my plugins to behave properly please try and ask in Realmac Software’s excellent support forum.
I will try to handle license issues during my vacation but the response time may be a little longer.
Away on vacation for a week
I will be away for short one week holiday starting tomorrow. During this period I will most likely not be able to handle any support or license issues since i’m running this by myself. If you have urgent issues getting one of my plugins to behave properly please try and ask in Realmac Software’s excellent support forum. There are many knowledgable gurus there that might be able to help you out until i’m back. For license issues I hope you can wait until the first weekend in May when i’m back again. Until then I won’t be able to do anything.
@stash v1.3.2
A bugfix release of @stash is now available for download. It contains a fix related to the upcoming RapidWeaver 4.2.2. This update is recommended for everyone that is using @stash no matter if you are using RapidWeaver 3.6.x or 4.x.
If you want to see the full list of changes you should check the changelog.
So go to the download page and get your copy of @stash v1.3.2.