Hawkix Blog

Yes ! I’ve just released PG4WP 1.1.0, and it is the official release having support for WordPress 2.9.x series

Many thanks to all of you who tested the development releases and gave me feedback and patches to make PG4WP better.

There are still some annoying problems (read more here), but they are in the TODO list for the next release.

Here are some of my ideas for the future :

- resolve most problems introduced by rewriting rules

- build up some kind of “modularized” support for WordPress’ plugins that need special handling

- have WordPress’ import feature work correctly at least with WXR files when using PG4WP

- convert PG4WP into some kind of Framework to easily integrate support for other databases (maybe I’ll call this DBs4WP ?)

- maybe build up a SQLite version, but are there people interested ?

It is time for you to give me any other ideas or wishes, just comment on this post

PGP4WP 1.1.0rc3 is out, integrating some patches transmited by Boris HUISGEN (many thanks to him).

I tagged this release as stable, but it still needs testing before I remove the ‘rc’ status.

See the changelog if you want to know what has changed.

Please vote in the plugin directory if it works for you.

[Update] A bug was introduced in PG4WP 1.1.0rc3 when handling permalinks, so I released a quickfix in 1.1.0rc4 that shouldn’t have the problem.

You can download PG4WP 1.1.0rc4 from the plugin directory here.

PG4WP 1.1.0 is almost ready for release.

All I need now is some feedback from people who can test the latest development version.
You can leave a comment to this post to give your feedback.

Fresh install of WordPress 2.9.1 seems to work smoothly, at least with PHP 5.2 and PostgreSQL 8.3 (this is my test/dev setup).

Upgrading from WP 2.8.6 to 2.9.1 works ok, there is just one query that generates an “INDEX not found” during the upgrade (for my testing database), this is a non blocking error.

If you are brave enough to test upgrading  from WP 2.8.6 (or any older release) to WP 2.9.1 please note that you should upgrade PG4WP before you start WordPress’ upgrade.
Don’t forget to make a complete backup of your data before trying this.

Important note : the ‘db.php’ from the development archive has PG4WP_LOG_ERRORS set to true, so if you don’t want these logs don’t forget to change it after copying the file to ‘wp-content’.

Here is the download link to the latest development version of PG4WP

Some of you may have noticed that 2 new releases of PG4WP were recently published (1.0.1 and 1.0.2).

Be warned that these new releases are not intended for WordPress 2.9.x, they are aimed at reorganizing files an directories and small enhancements.

Here is the list of changes :

= 1.0.2 =
* Updated support for plugin zdMultilang 1.2.5
* Got rid of some remaining hardcoded table prefix
* Added the possibility to log only errors

= 1.0.1 =
* Reorganisation of directory structure
* Updated installation procedure
* Changed the fake server version to 4.1.3
* Added support for Unix socket connections (just leave the “host” field empty when installing)

I’m now working on update for complete support of WordPress 2.9.1 (upgrade from 2.8.X AND fresh install), version 1.1.0 should be ready in a few days.

Wow ! Time is going so fast …

WordPress 2.9 seems to break compatibility with PG4WP 1.0.0, which is unsurprising.
Whereas I’m watching new releases of WordPress, I’ll wait some days after the bugfix release (version 2.9.1) before I start to work on updating PG4WP to make it work with WordPress 2.9.

While I’m working on this new release that will be numbered “1.1.0″, please note that 2 patches were developped by users of PG4WP (thank you for your work guys) :

• Stéphane Mariel : http://www.mariel.fr/docs/driver_pgsql.diff
• balrog-kun : http://www.openstreetmap.pl/balrog/wordpress-pg4wp-update-2.9.1.patch

There is not much work, but I want to test as much as possible before I publish the next release of PG4WP.

Here are the main goals for this planned 1.1.0 release :

1. Should work with at least WordPress 2.8.4 (existing installation)
2. Should work with WordPress 2.9.1 (fresh install)
3. Should upgrade smoothly from 2.8.4 to 2.9.1

WordPress 2.8.1 has been released.

I couldn’t use the automatic upgrade feature (I don’t think PG4WP is the reason), but manual upgrade didn’t raise any problem.

My blog doesn’t seem to have any problem since the upgrade, so PG4WP works with this new release .

You can read more about WordPress 2.8.1 here.