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.

Phoenixheart

This plugin displays a greeting message to visitors that come from different urls (known as referrers). For example, you may want to welcome Diggers with a message that reminds them to digg your story, or you may want to ask Del.icio.us users to bookmark your post, and so on.
Not only about a cool greeting box, it greatly helps to more efficiently interacts with your readers and build a better relationship between you (your website) and them.
<h3>Features</h3>
<ul>
<li>A pure AJAXed admin interface with elements tidily divided into tabs. Entries can be added/modified/(de)activated/deleted without the need to reload the entire page, or even with just one click. Starting from 3.2, there are even bulk actions!</li>
<li>The greet box position can be set to before, after, or (starting from 3.2) both before and after the post. A <a href="http://www.phoenixheart.net/2008/11/referrer-detector/#custom_tag" rel="nofollow ugc">custom tag</a> can also be used in case you don’t want to show greetings on every post.</li>
<li>Users can also put a tag (<code><?php if (function_exists('referrer_detector')) referrer_detector(); ?></code>) into the template to show the greet box anywhere of choice.</li>
<li>Excluded URLs can be specified in order to hide the greet box from specific users (like ones from Google Reader).</li>
<li>A * wildcard character can be used in both referrers and excluded URLs. For example: google.* will apply for all localized Google domains.</li>
<li>Multiple URLs can be merged into one entry, seperated by commas. For example: del.icio.us,delicious.com.</li>
<li>Ability to include WordPress attributes like url, title, author, category etc. into the greetings.</li>
<li>A STAT panel to get data reporting about the visitor statistic.</li>
<li>Many installed-by-default entries (which can be restored anytime with one click). Upon installing, you will have these entries available:
<ol>
<li>9 rules</li>
<li>Bing</li>
<li>BuySellAds</li>
<li>Del.icio.us and Delicious.com</li>
<li>Digg</li>
<li>Gizmodo</li>
<li>Google</li>
<li>Lifehacker</li>
<li>Live Search</li>
<li>Reddit</li>
<li>StumbleUpon</li>
<li>TechCrunch</li>
<li>Technograti</li>
<li>TechRadar</li>
<li>Twitter</li>
<li>Yahoo!</li>
</ol>
</li>
<li>Compatible with caching plugins, since the core is written and run in JavaScript which is normally not cached.</li>
<li>Automatically detect user’s country and display the localized greetings (if any).</li>
<li>Ability to backup and restore entries, excluded URLs, and options, very convenient for transferring between sites.</li>
<li>Welcome box now can be shown in lightbox style using <a href="http://www.ericmmartin.com/projects/simplemodal/" rel="nofollow ugc">SimpleModal</a> jQuery plugin.</li>
<li>Optimized OOP code allows extreme readability and easy modifications for other plugin developers.</li>
</ul>
<h3>History</h3>
<ul>
<li>4.2.1.0</li>
</ul>
<ol>
<li>Temporarily removed Backup/Restore feature for security reasons.</li>
</ol>
* 4.2.0.3 
1. Add Bing and BuySellAds entries. You can either reset the entries or create on your own using the new icons inside referrer-detector/images/icons/ directory 
1. Deleting the plugin now removes all options and data – Don’t try it 😉 
1. Several fixes and enhancements 
* 4.2.0.2 Raise compatibility 
* 4.2.0.1 
1. Added an option to display the welcome box in light box style 
1. Fixed several IE bugs 
* 4.1.0 
1. Welcome box CSS rewritten 
1. Added ability to optionally display related posts 
* 4.0.1 – A hot fix attempting to fix allow_call_time_pass_reference problem 
* 4.0 
1. Completely rewritten code – now optimized OOP 
1. Data are now stored in database for better security 
1. Introduced the ability to backup entries, excluded URLs, options (you can choose from these 3) 
1. Introduced the ability to add localized messages to welcome user visiting from different countries. 
1. STATs reporting is now using Google Chart 
* 3.2 
1. Introduced Bulk Actions 
1. Supported wildcard (asterisk character) in both referrers and excluded URLs, for example google.* matches all Google domains. 
1. Introduced the ability to merge several URLs into one entry, seperated by commas. For example: del.icio.us,delicious.com 
1. The greeting box can now be place BOTH before and after a post. 
1. Some minor graphic changes and bug fixes. 
* 3.1 
1. Fix the javascript bug on IE that prevents the greeting box from being shown up. 
1. The javascript files are now <a href="http://www.crockford.com/javascript/jsmin.html" rel="nofollow ugc">minified</a> instead of <a href="http://dean.edwards.name/packer/" rel="nofollow ugc">packed</a> to improve performance. 
* 3.0.2 Made a mistake in 3.0.1 
* 3.0.1 Fixed the bug that made the home page XHTML invalid 
* 3.0 Added the Stats panel. Now the plugin can show (customizable) stats of visits from different referrers from time to time. 
* 2.2.0.1 Fixed the javascript bug when jQuery library is not included by default. 
* 2.2 Added ability to include search terms into the greet box. Supports almost all common search engines. 
* 2.1.1 A small fixed on form serialization and a (possible) security flaw. 
* 2.1 A minor release, introducing the ability to restore the entries to default. 
* 2.0 Second major release, which has some important changes: 
1. A much much clearer admin interface with tabs, along with some enhancements. 
1. An option to not show the greeting box for visitors that come from specified URLs (“excluded” ones), for example Google Reader. The list can be edited easily via admin panel. 
1. Users can now put a tag (<code><?php if (function_exists('referrer_detector')) referrer_detector(); ?></code>) into the template to show the greet box. 
1. Some javascript files are packed to save bandwidth and loading time. 
* 1.2 Several important fixes and improvements. 
1. Fixed the bug when multiple greet boxes are shown if the page is filled with multipe full posts (such as homepage). 
1. Fixed the bug in the initial SQL data where the default RSS feed url is set to mine (tooo bad I forgot to check it). 
1. Fixed the javascript error when the page has no referrer. 
1. Update the installation and FAQ section. 
1. And some little stuffs… 
* 1.1 Better support to work with cache plugins. Now the generic options take effect without the need to delete the cache. 
* 1.0.1 A quick fix for caching problem (if cache is enabled and the first user has no referrer, the plugin will fail). 
* 1.0 Initial version

Referrer Detector

Helps your blog detect where the user comes from and automatically displays the corresponding greetings.

Mobile Detector vs Referrer Detector