Jump to content
justb3a

Module: Mobile Detect

Recommended Posts

The Title of the referenced topic has been edited, per your request

Share this post


Link to post
Share on other sites

I've just installed it on a PW 3.x site. 

It seems to detect Desktop correctly but I think it's returning an empty string for mobile. 
Haven't tested for Tablet but for my purposes I can live with this as I'm only interested in whether it's Desktop or not.

Will update if it can't detect Desktops correctly.

            if (wire(config)->mobileDetect->deviceType<>'desktop') {
				....
			}

 

Share this post


Link to post
Share on other sites

I just wanted to update saying the module doesn't work.

The problem is that the actual PHP module it depends on, mobiledetect.php is using  $_SERVER['HTTP_USER_AGENT'] which is an outdated way of detecting devices from the server.  It failed on Safari where it couldn't distinguish whether you were using it from the Desktop or a mobile device.

(You could argue PHP is probably not the way to go, compared to JS but that's another post )

I must have tried every PHP based solution out there in the last couple of weeks.
The only thing that has worked for me is UserAgentInfo.

I'm posting an example here, in case some one wants to update this module :)
 

function IsMobile() {

    $ua =  UserAgentInfoPeer::getMy();
    $mobile = $ua->isMobile();
    return $mobile;
}

P/S  You will need to add a reference to this class (You may need to change the path to suit your code structure)

require_once(__DIR__.'/../vendor/UserAgentInfo/UserAgentInfoPeer.class.php');

and then you may need to configure UserAgentInfoConfig class if the caching mechanism (Redis by default) is not what you want. Just change the CACHE_CLASS_NAME to the class you want.

    //const CACHE_CLASS_NAME = 'UaiCachePhpredis';    //Not installed locally
    //const CACHE_CLASS_NAME = 'UaiCacheMemcached';   //Not installed on Provider
    //const CACHE_CLASS_NAME = 'UaiCacheAPC';         //Not installed on Provider
    const CACHE_CLASS_NAME =  'UaiCacheDebug';



FYI I had to go for the non cached version (UaiCacheDebug) because of the hosting solution we currently have (i.e. el cheapo solution)


 

Edited by FrancisChung
More info

Share this post


Link to post
Share on other sites

@FrancisChung Thanks a lot for your feedback and hints. The collaborators of the detection library are working on a new release.

Quote

Still working on 3.0.0 branch to provide you with device detection! We're really excited on this one! We would like to speed this up, but life and family gets in the way ;)

As soon as the release has been published, I'll update the module.

Share this post


Link to post
Share on other sites
On 9.3.2017 at 3:03 PM, justb3a said:

@FrancisChung Thanks a lot for your feedback and hints. The collaborators of the detection library are working on a new release.

As soon as the release has been published, I'll update the module.

 

hmm … module didn't work (pw 3) but when i use the detection library and it works

// Include and instantiate the class.
require_once 'Mobile_Detect.php';
$detect = new Mobile_Detect;
 
// Any mobile device (phones or tablets).
if ( $detect->isMobile() ) {
 
}

 

Share this post


Link to post
Share on other sites
10 minutes ago, ngrmm said:

hmm … module didn't work

Probably because the module is outdated by 2 years. Last commit was at Sep 7, 2015

  • Like 1

Share this post


Link to post
Share on other sites

I just updated and tested the module, it should work correctly with PW3. :)

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

first, thanks for this cool module!

I have a question: Is there a way to detect the browser and show it by name? Like firefox, safari or chrome?

Share this post


Link to post
Share on other sites

Hi. Nice module! Exactly what I was looking for to make my main nav-bar conditional (if desktop, hovering drops-down my menu but clicking goes to page, if tablet etc., clicking just drops-down). Perfect! Thanks.

echo "<li class='dropdown'><a href='". ($config->mobileDetect->deviceType == 'desktop' ? $child->url : '#') ."' data-hover='dropdown'>{$child->title}<b class='caret'></b></a>";

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
×
×
  • Create New...