Permalinks - Standard and Mobile Sites

Hi Steve,

So you want to have two different permalinks for each record?  Or the presence of the /mobile/ prefix to indicate that a different viewer should be used? 

There's no support built into the plugin for anything like that right now.  I'm wondering if you could use the presence of a cookie to indicate which "view" (standard or mobile) of the page should be used.  And how does the "responsive" work?  Does it redirect to the other folder?  I'm also wondering about SEO issues from duplicate content on the different urls.

If you can let me know some more details I'll see what I can think of.   You might be able to address it with some simple custom programming to check for /mobile/ on permalinks. We'd have to see what was involved in that and make sure it didn't cause any other issues.

Hi Dave,

Okay, wasn't sure if I was missing something as we've just recently got into using the Permalinks plugin.

And yes, I was referring to the presence of a "/mobile/" prefix to indicate that a different viewer should be used. For this scenario there's a full Standard site and a full Mobile site, same page names (viewer names) for both "views" - the mobile site would be within a "/mobile/" folder (separate markup, separate style sheet, etc).

I guess basically it would be permalinks handled in a relative fashion (for this scenario).

As permalinks, Standard as domainName.com/Cool-Product/ and Mobile as domainName.com/mobile/Cool-Product/ (each page would actually be domainName.com/productDetail.php?1 and domainName.com/mobile/productDetail.php?1). I believe we're thinking along the same lines to accomplish this. The permalinks dispatcher would then know it's a request from the mobile site and put "/mobile" after "domainName.com" and before "/Cool-Product/". For SEO, I don't think it would be an issue since the mobile site would be displayed to devices detected as mobile.

For a responsive designed website this situation would never present itself since there would be no "mobile site", it's just the one site with appearance changing based on the size of the device screen. This situation would also never present itself for sites hosted on platforms supporting subdomains since the mobile site can easily be set as mobile.domainName.com or m.domainName.com as the absolute link structure will work the same as the standard site.

My goal is if a client uses a WYSIWYG editor to link to a Permalink CMS page it will work on the Standard and Mobile sites without issue.

Best Regards,
Steve

Hi Dave,

It just dawned on me what you mentioned with the cookie... For non-responsive sites, this entire situation could be avoided by having a single set of files serving the "view" change based on conditional. Note to self, drink more coffee...

Thanks, Dave.

Best,
Steve

Hi Steve

Just want to confirm you have this all sorted out. If there is anything else we can help with, let me know :).

Hi Ross,

Yep, I'm all set :) Thanks!

Steve

Hi Jesus,

I ended up using a session variable that was set by the result of PHP Mobile Detect script. Each file (page) would then serve the Standard or Mobile views based on the "site version".

In my case I used a session var labeled "SITEVERSION" and had the "view" toggled based on if it was set as "mobile" or "standard".

The PHP script I use can be found here:
https://github.com/serbanghita/Mobile-Detect
or
http://mobiledetect.net/

Setting the session var portion of the code:

    if ($detect->isMobile() && !$detect->isTablet()) { 
      $_SESSION['SITEVERSION'] = 'mobile'; // set site version
    } else {
      $_SESSION['SITEVERSION'] = 'standard'; // set site version
    }

I wrapped my Standard and Mobile site code (same file/page) in a conditional having the appropriate version served.

Hope that helps. Thanks!

Steve

Hi Steve,

This looks really neat and interesting, will take a closer look during the weekend or probably sometime during nights this week.

Thanks a lot for the info!

Jesus