WPtouch 1.9.9 Released Into Yonder Wild! (UPDATED)
UPDATED: WPtouch 1.9.9 introduced a bug which has been fixed in WPtouch 1.9.9.3. Please upgrade ASAP if you’re experiencing the issue.
Today we’re releasing an update to WPtouch to address a few issues which have been reported in the last while, and also add and revise a few existing features.
Tricky Fixes
Of note in terms of bug fixes are a fix for the admin page failing to load on some hosting setups, and a fix for some mobile browsers that have issues with return false;.
Fresh Features
In the what’s new category there’s been improvements to the comments via ajax and for iPhone/iPod touch visitors leaving comments they’ll now see the unique keyboards built into the iPhone for entering urls and e-mail addressses.
We were working on client-side text-size changing, but that’s not quite prime time so it hasn’t been included in this update.
Below you’ll find the complete list of changes.
Changelog
- Added HTML5 types for comment url and email (devices capable now show unique keyboard layouts for these inputs)
- Added and refined jQuery code, effects
- Revised post/page image sizing auto-detection features
- Changed the way Ajax comments work – will now work for everyone
- Changed code referencing javascript:return false; to javascript:void(0);
- Changed admin panel to stop using Ajax that would sometimes fail to load
- Removed comments-ajax.php from theme (not needed anymore)
- Removed ajax comments option from the admin (not needed anymore)
- Removed obsolete code orphans from old code methods
- Bug fixes
The update notification should appear in your WordPress admin shortly.
30 Comments
-
4 months, 3 weeks
waiting for beta build of 2.0
-
4 months, 3 weeks
1.9.9. breaks my site on a BB Storm browser. Haven’t checked on an iPhone or Android-based phone yet.
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘WPtouchPlugin::WPtouch_parse_request’ was given in /…/…/plugin.php on line 414
-
4 months, 3 weeks
Confirmed same error on Android (1.5 via Droid Eris).
Gonna comment out that line now.Literally installed 1.9.8 for the first time, then upgraded to 1.9.9 and ran into it… still not dissuaded… fantastic plugin.
-
4 months, 3 weeks
Commenting that line out worked!
Looks to be running smoothly now and everything is in order. -
4 months, 3 weeks
Hi! After the latest update i got this error message: Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘WPtouchPlugin::WPtouch_parse_request’ was given in /home/1/r/rockblogg/www/wp-includes/plugin.php on line 414
-
4 months, 3 weeks
Same problem – gave me that error on my pc version as well. I’ll try that fix.
-
4 months, 3 weeks
I see thumbnails on the homepage iphone is that coming with 2.0?
-
4 months, 3 weeks
I have unchecked both:
‘Enable Categories tab in the header’
AND
‘Enable Tags tab in the header’
but now with version 1.9.9+, they are visible (not honored). This option was honored with the 1.8.3 version I just overwrote.
Please address this. This plugin is very much appreciated. Thanks !
-
4 months, 3 weeks
I found why it’s not honoring the options. There is no conditional to check if either are enabled/disabled and the default is to just show them. It appears the same applies to the plugin’s login mechanism. While uncheck, it’s still visible on mobile page.
-
4 months, 3 weeks
Good to hear Juan! It’s a big plugin under the hood and we do our best to try and cover the angles in testing… Sometimes the roaches slip through the cracks!
-
4 months, 3 weeks
Normal Opera 10.50 and Opera mini are the same =(
-
4 months, 3 weeks
After upgrading to this version, my all desktop opera 10.50 (build 3296) visitors will see webpage as mobile version.
Can you fix that?
-
4 months, 3 weeks
I love your new updates and how easy it is to install this. I even got some more people using it after this post: http://scottgale.com/blog/setting-up-an-iphone-wordpress-plugin/2010/03/06/
Also, smart move using HTML5. You might as well utilize it since the browser understands it.