hanger

WPtouch 1.3.1 Released: Bug Fixed, More

We apologize for the nuisance of updating again and again. So instead of just baking the code fix into this point release, we’ve also done some further optimizations to make it worth the while, bringing the .zip file here on the website to only 211KB!

Bug Squishing

The particular fix we’re talking about affected sites veiwed in Safari- WPtouch was being shown in it as well, instead of just the website’s theme. No other browsers were affected.

Switch Code

Please also bear in mind if you’re upgrading from 1.2.1 or earlier that you’ll have to manually remove the switch code from your website’s theme. We no longer require your manual editing of the theme, and instead inject the code into your footer automatically.

Upgrade Reminder

For those of you with custom icons, please bear with us until WPtouch 2.0 is released. When it is, you’ll no longer have to keep replacing the images you place into icon-pool- there will be a separate directory created which won’t be overwritten that you can put both custom icons and themes into.

For now, backup those icons when you update WPtouch, and replace them afterwards.

It’s All You

Thanks again to everyone who writes in and provides us with excellent feedback and help sorting through various issues. It’s because of you that WPtouch is the success that it is.

vines

3 Comments ↔ “WPtouch 1.3.1 Released: Bug Fixed, More”

  1. 1
    08-22-08
    1:50 pm
    Tae Kim Said

    Minor point but the Settings page still mentions Prototype. My understanding is it’s now jQuery?

    Also, comments on pages doesn’t seem to work for me even after turning it on.
    http://www.guidetojapanese.org/blog/about/

    Finally, the “Header Title” keeps adding a slash in front of the single quote. I solved it by using a Japanese version ’ instead of ‘ but you might want to check it out.

  2. 2
    08-22-08
    1:51 pm
    Tae Kim Said

    Oh and by the way, forgot to mention what a great plugin! Can’t wait until it’s compatible with WP Super Cache.

  3. 3
    08-22-08
    6:42 pm
    Dale Mugford Said

    @ TAE… fixed in 1.3.2… and the Super Cache will likely involve .htaccess meddling.

vines

Offer A Timeless Opinion