Hawkix Blog

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.

PG4WP is now present in the plugins directory at WordPress.Org, allowing for a direct access to the latest versions and the changelog.