Aug 24

WP-Slimbox2 1.1.3 Released!

This is more of a fix than a major updated, but as several people noted, the overlay broke in WordPress 3.6. This was tied to an upgrade in jQuery. Christophe Beyls upgraded the original Slimbox2.js, so I’ve finally gotten around to doing the same for WP-Slimbox2.

I still hope to implement a more significant update in the near future!

6 comments

Skip to comment form

    • john on August 26, 2013 at 4:52 pm
    • #

    With the new update installed it breaks functionality with livewriter, throwing up errors with xmlrpc, deactivating the plugin cures this but then obviously lightbox stops working

      • Greg on August 27, 2013 at 9:53 am
        Author
      • #

      Since our support forums are down, I can’t test this myself, but I suspect the problem was tied to my saving the index.php as UTF-8 encoded (per plugin documentation), but perhaps I should have left it as ANSI, or UTF-8 without BOM. If you know how, and want to give it a shot, let me know what results you’ve got. Otherwise, I’ll try and throw something together this evening to test it.

    • Paolo on August 27, 2013 at 2:22 am
    • #

    In my website don’t work and break the admin backend.

    The other plugin that I have is

    Awesome Flickr Gallery
    Google XML Sitemaps 4.0beta
    Jetpack by WordPress.com
    Social Media Widget
    WordPress Backup to Dropbox
    YITH Maintenance Mode

    on wordpress 3.6 with Esplanade (http://www.onedesigns.com/wordpress-themes/esplanade-free-wordpress-theme) theme

    • Paolo on August 27, 2013 at 2:23 am
    • #

    This is the error that I see when I try to activate the plugin

    The plugin generated 3 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

      • Greg on August 27, 2013 at 9:53 am
        Author
      • #

      Since our support forums are down, I can’t test this myself, but I suspect the problem was tied to my saving the index.php as UTF-8 encoded (per plugin documentation), but perhaps I should have left it as ANSI, or UTF-8 without BOM. If you know how, and want to give it a shot, let me know what results you’ve got. Otherwise, I’ll try and throw something together this evening to test it.

        • Paolo on August 28, 2013 at 1:54 am
        • #

        I’ve saved the index.php as ANSI and when I active the plugin it doesn’t show me any the error.

Comments have been disabled.