Today we’ve tagged WPtouch Pro Beta 2 for release. Below you’ll find the release notes accompanying it.

Known Deficiencies

These are things which we know either don’t work or haven’t been added yet:

• Disqus and Intense Debate issues (these plugins will be supported later)
• Current themes are feature/styling incomplete
• Page/Menu area in admin has some inconsistencies across different browsers

Focus Areas for Testing:

• Admin functionality, performance, usability
• Automatic upgrade process
• WordPress 3.0
• Web-app mode in Classic and Skeleton

Changelog:

• Fixed: Garbled tooltips on translated multibyte characters such as Kanji
• Fixed: Plugin information overlay would die on other plugins
• Fixed: Tooltips with double quotations in them
• Fixed: Warning for htmlspecialchars on PHP4
• Fixed: Incorrect icons on custom templates such as Archives and Links
• Changed: Settings architecture for admin
• Changed: Tooltips appearance in admin
• Changed: Style fixes for Skeleton
• Changed: Header menu, icon style changes for Skeleton for better cross-browser compat
• Changed: Some admin form buttons switched to divs for Ajax purposes
• Changed: Switch link appearance on desktop theme is now bigger, bolder
• Added: Full translations for Japanese, Spanish, French, and Italian. German translation is still partial
• Added: Ability to render a custom WPtouch setting
• Added: Ajax submit for admin panel
• Added: Web-app mode in Skeleton, Classic (including loading image)
• Added: Theme settings tab for web-app mode, status-bar color option
• Added: New functions for iPhone meta tags in theme header.php, now handled by a theme function
• Added: Custom “dark” class for the body for custom page templates
• Removed: Unused beta code, functions from core files

Today we’re excited that Apple has officially released OS 3.1 for iPhone  & iPod touch, bringing a few new features and several bug fixes.

WPtouch 1.9.3 was also released, and brings with it a new feature and several bug fixes as well.

In 1.9.3 you can now choose to disable Ajax comments as the default method for commenting. We think Ajax comments are great (especially on a mobile device), but they bring with them some issues, and don’t always work right on every install or with every other plugin, so we’ve added this feature as a failsafe for those who’ve been reporting issues.

Other bugs were fixed pertaining to stability and javascript, the admin, and more.

We wanted to get some of the lingering issues resolved before completing and releasing the Skins features, as well as languages support, both of which we feel we’re in the clear to add so look for those to come over the next little while.

As always you can leave feedback about any of our free, open-source WordPress plugins in our Support Forums.

Unfortunately, there’s just no way to test all the conditions that WPtouch is ultimately subjected to without a band of beta testers. We plan on putting one together for WPtouch 1.9 onwards, as we’d prefer to have strong point releases without the need for much maintenance, as we’re busy guys working on some great client projects, trying to, as George Bush would say “…put food on our families”.

That said, WPtouch 1.8.1 is out, and should be perfectly lovely for the vast majority of users.

For more details read the WPtouch 1.8 Post.

We’ve done it! 5 languages (not including English) are signed up for WPtouch 1.9.

They are:

• French
• German
• Mandarin Chinese
• Spanish
• Russian

As more of you write in offering your translation talents we’ll add you to the language list, but our goal is to have these 5 prepared and ready to go with the release of WPtouch 1.9, which we’d hope will be out sometime in April.

WPtouch 1.8: Stop Bugging Me!

Already we’ve found a potential couple of bugs with WPtouch 1.8, and we’ll work to resolve them ASAP. If you haven’t upgraded yet, there are a couple settings in WPtouch which may not work on your install:

• Custom Header Logo
  
• Alternate Background Image

If those two settings don’t affect you you can upgrade without issue as far as we know. We’ll likely have a maintenance update out in the next day or so.