Martin Kuplens-Ewart

Hello,

You can hide all tables on your site by adding the following to WPtouch’s Custom Code field:

<style type="text/css">
    table { display: none; }
</style>

To make it more specific, you could see if there is an ID or class applied to the table and add those to the selector.

E.g., if the table has id=”contact-table”, the code above would read

table#contact-table { display: none }

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

Hello,

This morning’s update should resolve the issue you were experiencing with the URL filter field not saving correctly.

As regards the URLS within /wp-content/upload/?–?neither WordPress nor WPtouch are involved in those. Your web server is producing what are called ‘Directory Indexes’. It is typically advisable to disable these via your sites htacess file (see https://www.htaccess-guide.com/disable-directory-listings/ for a guide).

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

Hello,

You may encounter that using one of the WordPress debug tools when viewing admin pages other than those for WPtouch Pro.

To avoid affecting other plugins’ admin pages and simplify admin code, we use the WordPress enqueue_script dependency feature to prevent theme and extension admin JavaScript loading unless you’re on a WPtouch Pro admin page.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

You may have a cache plugin configured that is interfering with WPtouch. Visit https://www.wptouch.com/support/knowledgebase/optimizing-caching-plugins-for-mobile-use/ for instructions on configuring a variety of popular cache plugins to work with WPtouch.

Hello,

Sites like ‘responsinator’ work by loading your site in a narrow viewport. They may be useful for checking responsive themes but since they do not fully emulate a mobile device, WPtouch identifies the browser as a desktop browser not a mobile browser.

If you’re working on a Mac, you can make use of Apple’s excellent iOS simulator to test and preview on the desktop.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

Hello,

It looks like those buttons are output by the desktop theme’s template (perhaps using widgets?). Since the mobile theme doesn’t have that code in its templates, the elements aren’t displayed.

Should you be interested in upgrading to WPtouch Pro, you’ll find the Mobile Content extension for WPtouch Pro allows you to customize content for individual pages to include links to those pages.

Thanks for letting us know!

For direct assistance with WPtouch Pro, don’t forget you have access to the WPtouch Pro support site, https://support.wptouch.com/.

Martin Kuplens-Ewart
Product Manager, WPtouch

The problem on the pinellashousing.com website was caused by some jQuery-dependent code (added by a different plugin) being executed before the jQuery library was loading.

An error still occurs on that page due to code from a Google translator script attempting to register an event handler with jQuery prior to jQuery being loaded. It does not, however, appear to be affecting the menu.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

You may want to check the content on those pages–if you have iframes, tables, and other content with inline CSS (switch to the code tab to see) that is forcing them to a large width, Google’s tool will flag the page as not mobile friendly.

Hello,

It looks like you have a cache plugin installed that is preventing the mobile theme from displaying. Additionally some styling issues appear to be affecting your site. You may want to ensure your plugins are all up to date and possibly consider disabling the Autoptimize plugin.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

Hello,

Can confirm WPtouch is working correctly on your site with iPhone 5. You may want to check whether they see a ‘Switch to mobile version’ link in the footer of your site. If they do, they’ve switched to the desktop theme and can use that link to get back.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

Hello,

Thanks for bringing this to our attention. Support for WPtouch Pro is handled via our support site, support.wptouch.com. If you’d like to log in there using the password included in your license email, our support team will be happy to help you resolve the issue.

Thanks,

Martin Kuplens-Ewart
Product Manager, WPtouch

This is caused by lines 14-17 of settings.php:

if ( is_admin() )
	require_once WPCF7_PLUGIN_DIR . '/admin/admin.php';
else
	require_once WPCF7_PLUGIN_DIR . '/includes/controller.php';

From the AJAX in plugins article (Note 2, https://codex.www.ads-software.com/AJAX_in_Plugins#Ajax_on_the_Viewer-Facing_Side):

Both front-end and back-end Ajax requests use admin-ajax.php so is_admin() will always return true in your action handling code

Hi JP,

The challenge here is that WPtouch’s theme has no ability to affect the styling (and thus dimensions) of the page included via an iframe, something that is common with all web browsers on all devices. On the Astore side the width of the iframe content has been set at a fixed 748px, so it will always exceed the available display space on a mobile device.

You may want to see whether Astore have different formats available that better fit a mobile device.

Thanks for your feedback! Because we delay loading WPtouch’s JavaScript files to optimize page load times, its functionality can occasionally be affected by errors caused by other plugins.

Our testing with GC Social Wall suggests that a (poor) assumption on their part is to blame. If the GC Social Wall plugin is active, it loads a fragment of JavaScript for every page load:

jQuery(document).ready(function(){
	var agragator = new Agregator(walls_to_load);
});

Although it looks fairly innocuous, a sharp eye will spot the problem immediately: the variable walls_to_load isn’t defined here. In fact, it is only defined when a ‘wall’ shortcode is output (from initializeWall() in GCSocialWall.php):

<script>
  var walls_to_load = <?php echo base64_decode($content); ?>;
</script>

Since the plugin appears to only support one ‘wall’ at a time, the easiest fix would probably be for the GC Social Wall developer to move the initial section of code quoted above from the gc_social_wall.js file to the script block injected by the initializeWall() function. Alternatively they could check to see if the ‘walls_to_load’ variable has been defined before attempting to use it.

Please do contact the GC Social Wall developer and suggest they update their plugin to address this issue!