Tubal

A lightweight detector of mobile devices, OSs & browsers that, optionally, allows your site to switch to a mobile theme when a mobile device is detected or when your users feel like it.
This plugin adds the class MobileDTS to WordPress.
<h4>Mobile Detection</h4>
On every request, this plugin will try to detect if the user is viewing your site with a mobile device or not. If he is, the detector will also give you some info about the device, browser and OS used.
Who will be happy with this detector?
If you need a fast and reliable way to detect if a user is visiting your site with a mobile device, then you’ll be happy. However, if you need precise information about the device used (other than OS and browser) such as screen resolution you need a detector such as <a href="http://deviceatlas.com/" rel="nofollow ugc">DeviceAtlas</a> or <a href="http://wurfl.sourceforge.net/" rel="nofollow ugc">WURFL</a>.
How to query the detector?
Use the method <code>MobileDTS::is($key)</code>. <code>is()</code> returns boolean <code>true</code> or <code>false</code>.
Example:
<pre><code><?php

if (MobileDTS::is('android')) {
 // User with a mobile device running Android OS
} else if (MobileDTS::is('ios')) {
 // User with a mobile device running iOS
} else if (MobileDTS::is('mobile')) {
 // User with a mobile device (any, even 10 years old mobile phones) 
} else {
 // User with a desktop device 
}

?>
</code></pre>
Available keys:
<ul>
<li><code>mobile</code> (Is it a mobile?)</li>
<li><code>other</code> (Any other mobile device)</li>
</ul>
Popular mobile devices
<ul>
<li><code>iphone</code> (Apple iPhone)</li>
<li><code>ipad</code> (Apple iPad)</li>
<li><code>kindle</code> (Amazon Kindle)</li>
</ul>
Mobile OS
<ul>
<li><code>android</code> (Android OS)</li>
<li><code>bada</code> (Bada OS)</li>
<li><code>bbos</code> (Blackberry OS)</li>
<li><code>ios</code> (Apple iOS)</li>
<li><code>palmos</code> (Palm OS)</li>
<li><code>symbian</code> (Symbian OS)</li>
<li><code>webos</code> (Hp WebOS)</li>
<li><code>windows</code> (Windows Phone OS and older)</li>
</ul>
Mobile browsers
<ul>
<li><code>ff_mobile</code> (Mozilla Fennec & Firefox mobile)</li>
<li><code>ie_mobile</code> (IE mobile)</li>
<li><code>netfront</code> (NetFront)</li>
<li><code>opera_mobile</code> (Opera Mobile or Mini)</li>
<li><code>uc_browser</code> (UC Browser)</li>
<li><code>webkit_mobile</code> (Webkit mobile)</li>
</ul>
<h4>Theme Switching</h4>
You can configure your site to automatically switch to a mobile theme when a mobile device is detected or when the user requests it (on demand).
Once the plugin is installed, a new submenu titled <code>Mobile Detector</code> is added under the <code>Settings</code> menu.
Theme switching is disabled by default. To enable theme switching simply select a theme to use as your mobile theme and the plugin will take care of the rest.
This plugin assumes your active theme is optimized for desktop screens only. So, if you’re using a responsive theme that adapts to any screen size you shouldn’t use the theme switching feature (don’t select a theme).
How it works:
<ul>
<li>On each page load, this plugin checks for the existence of a cookie that stores which theme (mobile-optimized or desktop-optimized) the user prefers to browse.</li>
<li>If the cookie exists, the theme the user expects will be displayed.</li>
<li>If the cookie does not exist (first-time visitor), this plugin checks whether the user is visiting your site with a mobile device or not and, if he is, your mobile-optimized theme will be used. Afterwards, a cookie will be set to store the user’s “initial preference”.</li>
<li>Anytime the user switches (you must create a link/button in your theme using the Template functions below) between themes, the cookie is updated with his preference so the site version (theme) the user expects will be displayed on future visits.</li>
</ul>
Template functions
<ul>
<li>
<code>MobileDTS::get_switch_theme_link()</code> Returns the current URL with an additional <code>switch_theme</code> parameter (set automatically to ‘mobile’ or ‘desktop’). You’ll need this function to create a link/button that allows users to switch between the desktop and mobile themes. See example below.
</li>
<li>
<code>MobileDTS::switch_theme_link()</code>: same as above but this one outputs the URL instead of returning it. URL is escaped.
</li>
<li>
<code>MobileDTS::get_switch_theme_name()</code> returns the type of the theme to switch to (either ‘mobile’ or ‘desktop’). Use this method together with <code>get_switch_theme_link()</code>. The type can be translated to your language (plugin uses wp’s <code>__()</code> function for ‘mobile’ & ‘desktop’ strings).
</li>
<li>
<code>MobileDTS::switch_theme_name()</code> same as above but this one outputs the type instead of returning it.
</li>
<li>
<code>MobileDTS::is_mobile_theme()</code> tells you wether your site is displaying to the user the mobile theme or not. Returns boolean <code>true</code> or <code>false</code>.
</li>
<li>
<code>MobileDTS::is_switcher_enabled()</code> tells you wether theme switching is disabled or not. Returns boolean <code>true</code> or <code>false</code>.
</li>
</ul>
Creating a ‘Switch to …’ link
Let’s create a switch link to allow the user to switch between the 2 versions of a site (themes):
<pre><code><?php if (MobileDTS::is_switcher_enabled()): // Optional but useful if you need to disable theme switching for a while. ?>

<a href="<?php MobileDTS::switch_theme_link() ?>">Switch to the <?php MobileDTS::switch_theme_name() ?> version of this site</a>

<?php endif; ?>
</code></pre>
Paste that code in your templates (usually in <code>header.php</code> and/or <code>footer.php</code>), enable theme switching and play a little.
Let’s suppose a user is viewing the site (http://example.com/home) for the first time with a mobile device and theme switching is enabled. The above code would output this link:
<pre><code><a href="http://example.com/home?switch_theme=desktop">Switch to the desktop version of this site</a>
</code></pre>

Mobile Detector

Nice and Simple

Lightweight detector of mobile devices, OSs & browsers. Optionally a mobile theme switcher.

cuongquach

ZDN Adblock Detector is a lightweight plugin that detects when visitors are using ad blockers and displays a friendly message asking them to disable their ad blocker. The plugin features:
<ul>
<li>Reliable adblock detection</li>
<li>Clean and modern overlay design</li>
<li>Customizable message and overlay content</li>
<li>Flexible modal closing options – let visitors close easily or enforce page reload</li>
<li>Multiple closing methods: X button, click outside, or main button</li>
<li>Smart modal reappearance control – configure when the modal shows again after being closed</li>
<li>NEW: Enable/disable toggle to turn popup detection on or off</li>
<li>NEW: Front page only option to restrict popup to homepage only</li>
<li>NEW: Popup logging system to track which users see the popup</li>
<li>NEW: Admin dashboard with paginated popup logs and analytics</li>
<li>Flexible JavaScript loading options (external or inline)</li>
<li>Optional minified script for better performance</li>
<li>Proper internationalization support</li>
<li>Lightweight and fast</li>
<li>Easy to install and use</li>
</ul>
<h4>Modal Closing & Reappearance Options</h4>
Version 1.0.5 introduces advanced modal control with flexible closing and smart reappearance behavior:
<ol>
<li>
Flexible Mode: Visitors can close the modal using multiple intuitive methods:
<ul>
<li>Click the X button in the top-right corner</li>
<li>Click outside the modal area</li>
<li>Click the main button without forcing a page reload</li>
</ul>
</li>
<li>
Force Reload Mode (Default): Maintains the original strict behavior where visitors must reload the page to continue
</li>
<li>
Reappearance Control: When modal closing is enabled, choose how the modal behaves after being closed:
<ul>
<li>No popup again (Default): Modal never appears again once closed</li>
<li>Popup each visit: Modal appears on every new browser session</li>
<li>Popup after N days: Modal reappears after specified days (1-365)</li>
</ul>
</li>
</ol>
Administrators can easily configure these options in the plugin settings to match their site’s approach to adblock detection.
<h4>Popup Logging & Analytics</h4>
Version 1.0.6 introduces comprehensive popup tracking and analytics features:
<ol>
<li>User Activity Tracking: Monitor which logged-in users encounter the adblock popup</li>
<li>Detailed Analytics: View popup counts, timestamps, and user agent information</li>
<li>Paginated Admin Dashboard: Browse logs with customizable page sizes (10, 25, 50, 100, 200 items)</li>
<li>Privacy Controls: Enable or disable logging as needed</li>
<li>User Management: Track individual users with display names, emails, and popup frequency</li>
<li>Quick Access: User names in logs link directly to their WordPress profile for fast management</li>
</ol>
The logging system helps administrators understand: 
* Which users are using adblockers 
* How often the popup appears to specific users 
* Browser and device information for better insights 
* Trends in adblock usage across your user base
All logging respects user privacy and only tracks logged-in users when explicitly enabled.
<h4>Enable/Disable Controls</h4>
Version 1.0.6 also adds granular control options:
<ol>
<li>Master Enable/Disable: Turn the entire popup system on or off instantly</li>
<li>Front Page Only: Restrict popup detection to your homepage/front page only</li>
<li>Logging Toggle: Enable popup tracking independently of the detection system</li>
</ol>
These controls allow administrators to fine-tune when and where the adblock detection appears.
<h4>JavaScript Loading Options</h4>
The plugin offers two methods for loading the detection script:
<ol>
<li>External File (Default): Loads the JavaScript from a separate file</li>
<li>Inline JavaScript: Embeds the code directly in the page</li>
</ol>
Some browsers like Chrome may block external JavaScript files that detect ad blockers. If the detector stops working, you can switch to Inline JavaScript mode in the settings.
<h4>Performance and Security</h4>
The plugin includes both regular and minified versions of the detection script. Using the minified version (enabled by default) provides: 
* Better performance through reduced file size 
* Additional protection against adblockers by making the code harder to detect 
* Faster page load times
<h3>Plugin Images</h3>
Banner: banner-772×250.png 
Icon: icon-256×256.png

ZDN Adblock Detector

Detects adblockers and shows a cloaking mask to users with active adblockers.

Mobile Detector vs ZDN Adblock Detector