Yes ! PostgreSQL for WordPress 1.0.0 is out
This means I think the code is stable enough to be used in the real world
I optimized a bit the code, mainly to have often used code reached faster.
Another big change is in the size of ‘db.php’ that cuts down from about 32kB to less than 1kB.
It was initially a copy of WordPress’ ‘wp-db.php’ with some changes in it, now it loads up the file from your WordPress installation making any needed change “on the fly”.
The main advantage is that I don’t have to keep my version in sync with WordPress’ one.
Please be warned that this new method requires PHP 4.3+ to work, so this becomes the minimal requirement (anyway you shouldn’t use an older version of PHP).
I’ve also changed the directory structure, so that the ‘pg4wp’ directory goes directly in ‘wp-content’ instead of going into the ‘wp-content/plugins’ subdir.
This is because PG4WP is not really a plugin, you need it to be installed and running before any plugin can be loaded.
If you enable debug logging, the log files are now written into ‘pg4wp’.
A ‘readme.txt’ file is included in the zip, describing PG4WP for the plugin directory at WordPress.Org
I’m still waiting for my account there to put PG4WP.
I use PG4WP to run this blog since I opened it, and encountered no real problem with it (only “not working features” that I corrected since then).
If you use PG4WP to run your blog (in fact this is true even if you don’t use PG4WP), don’t forget to make regular backups (and verify that you’ll be able to restore them in case anything goes wrong), ‘pg_dump’ is your friend if you are running PostgreSQL
If you installed any previous version, don’t forget to remove the ‘pg4wp’ directory from your ‘wp-content/plugins’ directory as this one is no more used.
Download :
PG4WP 1.0.0