Posts tagged ‘Testing’

[Update] PG4WP 1.1.0rc3

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.

[Update] PG4WP 1.1.0rc2

Time for some news about PG4WP.

Hawkix Blog is now running WordPress 2.9.1 using PG4WP 1.1.0rc2

I’ve tagged a 1.1.0rc2 release because I didn’t get much feedback until now.
‘RC’ means it is a Release Candidate, I feel confident about it being stable enough for production use, but it still needs testing.

Please note : error logging is active in this release, but you can disable it in ‘db.php’ that you have to copy in ‘wp-content’.

The ‘readme.txt’ file is up to date about installation, don’t forget to read it.

[UPDATE] Some people asked me were to download this release, so here is the direct link to the zip file in the wordpress plugins directory :)

PG4WP 1.1.0 en test

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