GigPress

Live performance listings for WordPress.

GigPress 1.3.3

Posted by Derek on Thursday, July 3rd, 2008 | 9

Just committed version 1.3.3 of GigPress, fixing a couple of bugs, and adding compatibility with the forthcoming WordPress 2.6 (as tipped off by Ozh.)

Details, as always, can be found in the release notes on the download page.

9 comments

  1. Jorge
    July 6th, 2008
    2:24 pm #

    The last couple upgrades break the language when updated straight from WP (it reverts to English). Uploading the languages folder cures it. Any idea why?

  2. Derek
    July 6th, 2008
    7:33 pm #

    @Jorge – does the ‘langs’ folder disappear after the auto-upgrade? Or does it appear to be corrupted or something? I just tried an auto-upgrade for a site both in the default language (English) and one in Spanish – both seemed to work just fine.

  3. Christian
    July 17th, 2008
    12:29 pm #

    I can’t make german language to work. Uploading the language folder again didn’t help. I installed the plugin for the first time on WordPress 2.6. What can I do? Thanks for your help!

  4. Derek
    July 17th, 2008
    3:10 pm #

    @Christian – you found a bug there that rears its head with WordPress 2.6 – just fixed this with version 1.3.4, available now.

  5. Jorge
    July 17th, 2008
    3:34 pm #

    It’s very strange. The langs folder is there, and the .mo file is there, and it’s in Spanish.

    Wait a minute – now even reuploading the langs file doesn’t cure it. I’m still on 2.5.1.

  6. Jorge
    July 17th, 2008
    3:36 pm #

    Hm, not so fast – uploading the es_ES file doesn’t cure it, but uploading the whole folder does. Does this ring any bell?

  7. Christian
    July 17th, 2008
    3:42 pm #

    Just upgraded – works perfectly. Thank you for your great work! Really nice work.

  8. Derek
    July 17th, 2008
    4:00 pm #

    @Jorge – can you let me know how the 1.3.4 automatic upgrade fares in this regard?

  9. Jorge
    July 24th, 2008
    8:04 pm #

    Sorry I commented here, Derek – the issue happened with the 1.3.4 upgrade.

Comments are closed.