Jan Reilink

Hi @kts915, thank you for your reply.

My intended use is exactly what “Sumit” states at http://wordpress.stackexchange.com/a/188897/27620:

How WordPress use it: WordPress do not use it for styling or adding CSS anywhere. WordPress use it to add or manipulate thing which should be only on mobile devices (regardless size and name.) e.g. to add touch scripts, add viewport, mobile class in admin header, adding mobile buttons.

To be frank (note: this is beyond the scope of this support ticket! But to eleborate the wp_is_mobile() usage) , I don’t want to display some ads on mobile devices.
My shortcode in my own site-specific plugin to accomplish this is:

function adsenseads300600() {
  $output = '<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
    <ins class="adsbygoogle"
      style="background-color: transparent;text-decoration: none;display:inline-block;width:300px;height:600px;"
      data-ad-client="ca-pub-yyyyyy"
      data-ad-slot="zzzzz"></ins>
    <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script>';
    
  if ( ! wp_is_mobile() ) {
    return $output;
  }
}
add_shortcode('showmyads300600', 'adsenseads300600');

My next step is to opt out from ads using a cookie, but that’ll take some more time.

• This reply was modified 9 years, 7 months ago by Jan Reilink. Reason: blockquote formatting

Thanks for your reply @codyarsenault!

It’s not quite what I meant, and maybe I didn’t explain myself well enough. But it’s not about using a separate mobile theme or plugin to create a mobile theme (kinda). Let me elaborate:

In WP-Super-Cache you can activate the WPTouch plugin for WPSC, without actually having WPTouch… (wait for it). Then comment out a line in plugins/wptouch.php (reference), and WPSC nicely generates static cache files for mobile devices, called index-mobile.html of example.

Note, these are no different than ordinary WPSC static cache files, but in your .htaccess or web.config file, you can rewrite visitors using a mobile device directly to the index-mobile.html(.gz)? files.

Doing so gives you the opportunity to use WordPress functions like wp_is_mobile() to present mobile visitors with a different user experience than ordinary computer users.

The problem with Cache Enabler: when I use wp_is_mobile() in my theme or plugin, and a visitor using a computer visits a post first, only that variant of the post is cached. There is no way to generate a mobile version anymore.

(please excuse the lengthy reply 😉 )