Unstable 1.0.0 beta3

ludo, Thursday 24 March 2005 19:30:00 PST

As promised, I have applied most of the patches Jerome sent me yesterday night and released 1.0 beta 3. I chose not to apply the following two patches:

  • query logging in DB_lite/MySQL.php, it's a good idea and very useful when you need to debug a SQL statement, but it's trivial enough to add/remove it by hand, and I prefer not to add code that will never be used in production

  • the

    'name'=>'post'

    context mapping used for WP compatibility, as it interferes with the comment registration cookies, rendering the whole site unusable; the patch is good though, so I guess I will have to rename the cookie vars after 1.0 is released

A huge thanks to Jerome which has spotted quite a few bugs, and worked hard for WP compatibility, something I'm not really interested in but which may be crucial for many. If everything works as expected, we may be able to release 1.0 stable in a few days.

Readers' Comments

  1. jerome

    Re: name=>post — that explains my feeling of deja vu, I thought I fixed this in an earlier release.

    Another compatibility note: WPFF uses ’s’ for static pages while WordPress uses it for search terms. I didn’t put this in the patch, but for anyone using a WordPress .htaccess file you can work around this by putting the following at the beginning of your index.php file:

    if (isset($_REQUEST['s']) && !isset($_REQUEST['q'])) {
    $_REQUEST['q'] = $_REQUEST['s'];
    unset($_REQUEST['s']);
    }

  2. jerome

    Removing name=>post breaks compatibility, but you can add this code to index.php to fix it (similar to above):

    f (isset($_GET['name']) && !isset($_REQUEST['p']))
    $_REQUEST['p'] = $_GET['name'];
    elseif (isset($_POST['name']) && !isset($_REQUEST['pagename']))
    $_REQUEST['p'] = $_POST['name'];

    And a few new bugs:
    - Version is being output as 1.0b1, should be 1.0b3
    - The pagename=>post context conflicts with pagename=>static, so I’d suggest using postname=>post instead.

  3. jerome

    There may be no “i” in “team”, but there should be one in the “if” above!

  4. ludo

    Argh you’ve lost me, too many contexts to keep track of :)

    Ah ok, it’s only the WP-compatible ones which are conflicting. Will fix it for 1.0 :)