PG4WP didn’t get any release for a very long time.
I recently had requests from users who wanted me to update it for WP 3.9 compatibility and some of them even sent me code to correct the problems.
So here is PG4WP 1.3.1 which seems to work ok with WP 3.9.2 (the latest stable release at time of this writing).
I integrated the corrections from Vitorio DELAGE’s article on his blog.
Please note I don’t have enough time to make complete testing, I just tested direct upgrade from WP 3.4 to 3.9.2 and it worked smoothly.
If you intend to use this new version don’t forget to :
1) Backup your database and data (at least the `wp-content` directory)
2) Update PG4WP
3) Update your WordPress installation
If you activate SQL error logging in PG4WP you will notice many errors about running ‘SELECT @@SESSION.sql_mode’.
This is not harmful and you can ignore them.
Hopefully I’ll get some time to work again on PG4WP some time after WP 4 is released, stay tuned.
As always you can get the latest PG4WP release from the WordPress plugin directory
WordPress 3.4 was officially released yesterday, so here is PG4WP 1.3.0 !
PG4WP 1.3.0 is mainly aimed at PostgreSQL 9.1+ compatibility, but there are also some improvements on data import (to ease migration from a MySQL setup) and WPMU support (not much tested though).
I’ve run a bunch of tests over different version of WP (no plugin enabled at all) :
- Fresh install :
- WP 2.9.2 : OK (this is the least supported WordPress version from now on)
- WP 3.3.2 : OK
- WP 3.4 : OK
- Importing this blog’s data from WXR export (Tools>Export) :
- In WP 2.9.2 : OK
- In WP 3.3.2 : OK
- In WP 3.4 : OK
- Upgrading (after import) :
- From WP 2.9.2 to 3.4 : OK but had an error about `undefined function self_admin_url()` at the end of the upgrade process (I think it’s a WP 2.9 problem)
- From WP 3.3.2 to 3.4 : OK with no error at all
These tests were run using PHP 5.2.17 on Apache 2.2.17 using PostgreSQL 8.3.15 (sorry I couldn’t test on PostgreSQL 9.1).
Important note : if you have problems with creating new categories with an old install of WordPress/PG4WP you may have to run the following SQL statement in your PostgreSQL database :
SELECT setval(wp_terms_seq, (SELECT MAX(term_id) FROM wp_terms)+1);
This will correct the sequence value for your setup.
The next release will focus on optimisations and code cleanup.
Download PG4WP 1.3.0 from the plugin directory
WP 3.4RC1 was released recently, so I’ve run a bunch of tests (mainly setting a fresh install of WordPress and importing this blog into it) and everything seems to go well.
I’ll wait for WP 3.4 to be released before tagging PG4WP version 1.3.0, if you happen to run tests yourself please post a feedback.
I worked on import support with ‘wordpress-importer’ plugin.
Everything seems to work fine in my tests, so it should now be possible to migrate from MySQL to PostgreSQL by exporting and then importing back your data (using WP’s integrated Export/Import tools).
This may also work with other WordPress importer plugins, so please give it a try and tell me about your success
I’ve just tagged PG4WP 1.3.0b1.
This version integrates support for PostgreSQL 9.1+ and WPMU (not much tested though) and works with WordPress up to version 3.3.2.
As a development version it has error logging enabled by default (`PG4WP_LOG_ERRORS` in `db.php`).
If you happen to test it, please file a report (even on success) by commenting on this post indicating your versions (WordPress, PostgreSQL, maybe PHP too) and your installation type (upgrade from existing WP+PG4WP, fresh install).
WPMU users, please indicate if you tried `sub-domain` or `sub-directory` setup.
You can download PG4WP 1.3.0b1 from the developers page in the directory plugins (under `other versions`) :
If you ever wanted to run WordPress Multisite with PostgreSQL, it’s time to make a test run with the latest development version of PG4WP.
I’ve made changes so that everything seems to go fine (at least in « subdirectory » mode).
If you happen to try it, please file a report by commenting on this article.
Please don’t forget to indicate the following elements :
- PHP version
- PostgreSQL version
- WordPress version
- which mode you tested (« subdomain » or « subdirectory »)
To download the latest development version of PG4WP just click here
So much time since my last post !
I apologize to all of you who sent me messages I didn’t answer.
I’ve had much work in the last months and mainly off the Net, but I’m back on track and already started to enhance PG4WP to correct some bugs and add new features.
If you try the current development version it now includes support for PostgreSQL 9.1+ « out of the box », but it needs testing.
I’ve also tested fresh installing and upgrading to WP 3.3.2 (and also 3.4-beta4) and all seemed to go well.
I’ve had some contacts about WPMU, so I’ll try to work on it after the next release of PG4WP (which should come in the next few weeks).
PostgreSQL 9.1 introduces a change in the default value for the « standard_conforming_strings » parameter.
When this parameter is « on » (which is the new default), PostgreSQL will stop accepting the backslash character for escaping single quote in strings.
For now, if you want to use WordPress/PG4WP with any version of PostgreSQL starting with 9.1, you’ll need to set « standard_conforming_strings = off » in your « postgresql.conf » file.
I’ll try to find a solution for the next release of PG4WP so that it works « out of the box » with PostgreSQL 9.1+
PG4WP 1.2.0 had a bug that caused WordPress paging to not work, so it’s time for PG4WP 1.2.2 to come out !
This new release corrects this problem.
Also included are some code reorganising (for easier testing of the SQL rewriting code), and some changes to the install/upgrade handling code mainly for WPMU support.
Please note that WPMU does not work yet with PG4WP, but I still intend to get it working if it is possible.
Note : 1.2.1 had a regression so it shouldn’t be used at all.
Download : PG4WP 1.2.2
Since version 3.0, WordPress integrated multisite code into its core code, so I’ve recently tested setting up a network of sites on a dev environment.
Not so surprisingly it didn’t work, but the generated errors showed that it shouldn’t be very difficult to get it working.
WPMU will require code reorganisation, and enhanced support for upgrading functions.
I’m starting to work on these changes mainly because they will improve the overall quality of PG4WP.
If you are interested in PG4WP support for WPMU and want to help testing, please contact me by leaving a comment here or via the contact form.