Oh no…but wait, it's Christmas…

Did you miss the special day discount? Fear not…it’s Christmas time 🙂

You can still get a discount for my plugins but not as much as yesterday. Use any one of these two codes and you will receive a 25% discount on all items. This offer is valid until the end of Christmas day CET.

Discount code: OHNOIMISSEDTHESPECIALDAY or ITSCHRISTMASTIME

No comments

T-0…and here it comes…

Today is a very special day…i’m even more grownup than I was yesterday 😛 And to celebrate that I have lowered the price of my plugins to the amount of years i’m reaching today. And no, I will not tell you how much it is, use the discount code and do the math’s if you are just curious 😉

This offer is only valid 2010-12-19 CET, note the timezone. Once we hit 2010-12-20 here in central Europe the offer is gone.

Discount code: OMGITSASPECIALDAY

PS: In case you are wondering about the state and future of my plugins…they are still working without any major problems with RapidWeaver 5.0. But i’m going to go through them all soon and fix some minor issues. DS.

No comments

T minus 24 hours

…and counting…

Stay tuned for something special!

Comments (2)

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.

Comments (9)

Gone fishing…

Not exactly but it was a fun headline 🙂

This is just a post informing you about the current delay in responding to support issues.

For a while now I have not been able to
answer support requests as quick as I want. And this situation will remain for several more weeks.

The reason for this is that me and my family are moving to a new house which we have been building for a while. Between my dayjob and finishing this house there is not much time left for support unfortunately. But I do my best to prioritize the requests by putting purchase questions on top of the queue followed by urgent setup requests The other requests will be handled when time permits and that is mostly time consuming and hard to trackdown problems.

But rest assured that all these requests will be handled, at the very latest when we have finished moving which is in June. Until then I hope you can oversee that there are some delays for your requests.

Comments (2)

Backing up your blog with WP-DBManager

Working backups is a must in our modern life. And backups should be easy to make too.

But most of us that have a self-hosted WordPress blog doesn’t think of backups. Or we may think of it but we usually look in the control panel of our webserver only to discover that taking backups is way to difficult.

If your blog is hosted with a big hosting provider they probably have some kind of backup system. But don’t bet on it. They may have backups but maybe not for all of your stuff. And/Or maybe not as often as you would like, etc. It might also be difficult to restore such a backup in case something happens since you are not in control of your backup.

The most important part to backup is your database. Never mind the actual WordPress software or all the third-party plugins. They can easily be downloaded and installed again. But if you loose your database then all that really matters is lost.

So what can be done about this…

WP-DBManager, a simple, yet powerful, WordPress plugin that lets you set-and-forget backups of your WordPress database. Using this tool, and an email account that allows large emails you can have your blog backed up in no time.

Here is a tutorial on how to install and activate this plugin so that your database is backed up:
The Perfect Hands-Free Database Backup

PS: As a sideeffect you will almost get a phpMyAdmin tool inside WordPress using this plugin. DS.

Comments (3)

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…

Comments (6)

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…

No comments

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…

No comments

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.

No comments