Time for some news, and these are quite good.
The development version of PG4WP seems to work ok with WordPress 3.0-beta1.
I’ve improved the ‘db.php’ file that sets PG4WP up during WP’s startup to remove some annoying notices (they don’t appear in a « non-debug » install but still exist) and to remove potential fatal errors.
Upgrading from WP 2.9.2 to WP 3.0-beta1 works OK (you’ll get some errors about INDEX creations in ‘pg4wp_errors.log’ if you enabled it, but these can be ignored), you have to update PG4WP before you upgrade.
Making a fresh install of WP 3.0-beta1 works OK too, at least in ‘single blog’ mode (I didn’t test the Multi-blogs mode yet).
PG4WP now appears in the installed extensions and can be activated (in fact this has no effect).
You shouldn’t use the « extension update » feature from WordPress for now, this won’t work as expected.
A new release is on the way, PG4WP 1.2.0 will be out soon, hopefully before WordPress 3.0 official release … Stay tuned 
If you want to try out :
Here is a direct link to PG4WP development version
Hello Hawkix
I’ve tried to perform fresh install and generally I went ok with only few errors:
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
WordPress database error: [ERROR: duplicate key violates unique constraint "wp_term_relationships_pkey"]
INSERT INTO `wp_term_relationships` (`term_taxonomy_id`,`object_id`) VALUES (’0′,’0′)
However there is a small issue. I am unable to login after install. I tried to reset password and it didn’t help either. So is there any workaround? Or do you need some more logs to investigate it?
Best regards
Seba
I didn’t experience these errors when I tested a fresh install using the latest development release of PG4WP.
In order to investigate I need to know at least which version (exactly) of WordPress you are using, and also which release of PG4WP you are trying to use.
Please remember that for now there is no official release of PG4WP for WordPress 3.0 (but the development version has been tested with at least WP 3.0RC1).
I’m planning a release soon after I manage to get some time to make more testing.
Hawk
I am understand that you version is development one. That’s why I am open co-work to isolate encountered issues. I’ve tried following mixes:
- wordpress official ver3.0 and your latest dev version
- wordpress official ver2.92 and your latest dev version
- wordpress official ver2.92 and your latest official version 1.1.0
The first two configurations gave me the same errors as in my first post. The third configuration eventually start working. Between each attempt I had dropped database.
Send me mail if you need further details.
Regards
Seba
Are there any news on wp3 support?
I’ve had much more work than expected in the past months, but I’m going to work again on PG4WP in the next few weeks, so I hope to have WP3 fully supported during october.
Stay tuned
This version broke the image uploading: the thumbnail generation didn’t work anymore.
This happened because the insert_id of the generated post was always 0, because the query didn’t match ‘/INSERT INTO (\w+)\s+\([ a-zA-Z_"]+/’;
I believe this is a result of the $sql = str_replace(‘`’, », $sql); command being moved further down. Inserting this line somewehere around line 202 in driver_pgsql.php seams to fix this situation.
Regards,
Aart Jan