Skip to content

PG4WP 1.2.0 released !

PG4WP 1.2.0 is finally out !

This version has been tested with WordPress 3.2.1 and works OK.
It should also work with WP 2.9.2 (tested during development phase), and probably older versions as well (but untested).

If you are using an older version of PG4WP and want to upgrade, don’t forget to make a complete backup first (just in case something goes wrong), and try to follow these steps :

  1. Check that you are using PG4WP 1.1.0 and upgrade your WordPress to version 2.9.2 (if it is not your currently running version yet)
  2. Upgrade PG4WP to version 1.2.0 (the best is to remove `db.php`from `wp-content/` and `pg4wp/` from `wp-content/plugins/` and then to proceed as for a new installation, because the directory structure was reorganised)
  3. Verify that your setup is working correctly with PG4WP 1.2.0
  4. Upgrade WordPress to v3.2.1 which is the latest version tested

If you need support or help, you can use the WordPress.org support forum and open a new topic about your problem if one doesn’t already exists.

Here is a direct link to download PG4WP 1.2.0

Time for a release candidate (PG4WP 1.2.0rc)

I’ve juste tagged PG4WP version 1.2.0rc, which after complete testing should become the next stable version of PG4WP.

PG4WP 1.2.0b1 had a few regressions that caused some WordPress features to not work properly.
This new release fixes them and improve installation so that WordPress can now tell you if your login/password is wrong.

Here is the link for direct download : http://downloads.wordpress.org/plugin/postgresql-for-wordpress.1.2.0rc.zip

Please leave a comment if you happen to test it.

PG4WP 1.2.0b1 (Beta release)

I’ve just tagged PG4WP version 1.2.0b1 in order to ease testing.

You can download it from http://downloads.wordpress.org/plugin/postgresql-for-wordpress.1.2.0b1.zip.

This version should work with WordPress up to version 3.2.1 and includes  some improvements to generic plugins support.

Please note :

  1. if upgrading you should overwrite your ‘db.php’ with the one from the ‘pg4wp’ directory as it was split in 2 files in order to simplify future upgrades
  2. the ‘pg4wp’ directory can now be placed either in ‘wp-content/plugins/’ or ‘wp-content/’ at your choice.
    Putting it in ‘wp-content/’ will hide it from the plugins in your dashboard (it will still appear as a « drop-in plugin » though, which seems okay for me)
  3. this version is to be considered as « beta » quality (don’t forget to make backups before upgrading), but all my tests were successfull

If you try it, please notify me of your results by commenting on this post (please don’t forget to write the version of WordPress you tried to setup).

Some good news about PG4WP

First of all, I must apologize for not giving any news about PG4WP for a so long time …

I finally came back to PG4WP development, and already integrated a bunch of updates in the development release (which you can download from http://downloads.wordpress.org/plugin/postgresql-for-wordpress.zip ).

If your wordpress is currently running version 2.9.2 with PG4WP 1.1.0 (or the previous development release), you can upgrade to WordPress 3.2.1 using the following steps :

  1.  update PG4WP (replace all the files with the ones from the zip archive)
  2.  overwrite `db.php` in your `/wp-content/` directory with the one from the `pg4wp/` directory
  3. check that `db.php` has the correct configuration for you (error logging is enabled in the archive)
  4. upgrade WordPress with the method you like and you’re done

I’ve tested new install with WP 2.9.2, 3.0.6, 3.1.4 and 3.2.1

Some people asked me about how to have some plugins to work in WP with PG4WP.
I’m going to write some guidelines about this, but you must keep in mind that this may be really difficult for database intensive plugins (especially if they use direct mysql calls).

For now, PG4WP embeds some workarounds for Akismet and WP Stats that are provided with WordPress.
I need to think about the best way to handle plugins workaround.

I hope to have feedback about my recent modifications so I can build up a stable release quickly (maybe at the en of this week or early next week).

PS : This blog now runs WP 3.2.1 with the latest PG4WP development code

 

[Update] WordPress 3.0-beta1 is out, PG4WP development goes on

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

Here is a direct link to PG4WP development version

PG4WP 1.1.0 is out with WP 2.9.2 support

Yes ! I’ve just released PG4WP 1.1.0, and it is the official release having support for WordPress 2.9.x series :)

Many thanks to all of you who tested the development releases and gave me feedback and patches to make PG4WP better.

There are still some annoying problems (read more here), but they are in the TODO list for the next release.

Here are some of my ideas for the future :

- resolve most problems introduced by rewriting rules

- build up some kind of « modularized » support for WordPress’ plugins that need special handling

- have WordPress’ import feature work correctly at least with WXR files when using PG4WP

- convert PG4WP into some kind of Framework to easily integrate support for other databases (maybe I’ll call this DBs4WP ?)

- maybe build up a SQLite version, but are there people interested ?

It is time for you to give me any other ideas or wishes, just comment on this post :)

[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 needs testing

[lang_en]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

[/lang_en]

Le support de WP 2.9.1 arrive bientôt|WordPress 2.9.1 support is coming

[lang_fr]La version en cours de développement de PG4WP inclus le support de WordPress 2.9.1 pour les nouvelles installations, si vous le souhaitez vous pouvez tester cette version dans le répertoire des plugins (dans « Other Versions »).[/lang_fr]

[lang_en]The developpement Version of PG4WP has initial support for WordPress 2.9.1 fresh installs, you can test it and give your feedback as a comment to this post (please give some informations about your setup).

You can download this version in the plugin directory (in the « Other Versions » section).

As always, don’t forget to make complete backups before testing a development version.

Note : upgrading from WP 2.8.x is not ready yet (it works, but generates errors about indexes that may make your setup unusable after upgrade), I have some more work and testing before I put this part into the development version.[/lang_en]