I have a website that is using two different views, namely desktop and mobile. Generally for blogs hosted on Blogger will display a mobile version of your blog when combined ?m=1 at the end of the blog url.
My website is quite risky if the user turns using chrome or another browser to the desktop but with an additional open my web ?m=1
Now I ask.
Is it possible to prohibit the user opens the mobile version of my blog when he used the computer / PC / Laptop?
Please explain, thank you
We can detect the UserAgent of the browser and if it isn't mobile, then we can replace the query parameter m=1 with m=0 (which redirects to the desktop version)
Adding the following code to the <head> tag of the template should work (The UserAgent condition courtesy of What is the best way to detect a mobile device ) -
<script>
if(!/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent) && location.search.match("m=1") != null)
{
location.search = location.search.replace('m=1','m=0')
}
</script>
Note: Make sure that you are using the Custom Mobile template to make this work (In Blogger dashboard > Template tab > Gear Icon > Check Yes. Show mobile template on mobile devices. > Select Custom in Choose mobile template dropdown )
Related
Problem:
Web page with sms: and mailto: links fail on ios mobile safari browser. A click on the link redirects you to:
Safari cannot open the page because it cannot redirect to locations
starting with "sms:"
or
Safari cannot open the page because it cannot redirect to locations
starting with "mailto:"
These used to work just fine up until around two or three months ago. Now these fail on Apple mobile devices using the Safari browser.
Background:
I create responsive web pages for activity based teams. One of the things we do is provide a team roster. The roster includes links for telephone numbers, SMS text pages and Email.
To keep things simple, we are using simple web pages.
Because of security and privacy concerns, this content is only served via ajax call via node.js server after login. We're using a single node.js Express server to host the website content and manage http/api calls.
Generally a click on the link pushes the mobile device into the appropriate native app for a phone call, SMS text message or email.
This has been working great for a couple of years, on all devices.
Lately we're seeing the problem on iPhones... but...
Here's the really weird part. I've got three teams using this technique.. The failure is only on TWO of the three teams. SMS link works just fine there.
The "tel:" link works fine on all devices.
The failures only occur on two of the three sites for sms: and mailto: on the iphone. Things still work just fine on Android devices, on Windows and on MacOS. The problem is Apple mobile devices.
The two sites that have the failures are Progressive Web Apps, with a manifest.json file and service_worker.js. The site that works fine has neither of those. When I remove the manifest, and turn off the service worker there is no improvement.
All three sites hosted via App engine at Google Cloud. The two sites that fail are only using web_app.appspot.com addressing. The site that functions well is using a real URL, pointing to the app engine location.
Typical Code:
<li>
<div class="userName">Jane Doe</div>
<div class="phoneNumber">321-555-1234</div>
<div class="sms"><img src="../images/crosstxt-icon.jpg"></div>
<div class="email"><img src="../images/email-icon.png"></div>
</li>
I wonder if this will show the issue, if you open this up in the browser of your Apple mobile device:
Click here to create a SMS message.
<br>
Click here to create an email message.
Apparently that's a fail. You don't even get to see the run snippet button on my mobile device.
Testing, more testing...
I just figured out... if I save the site to my mobile device homepage, such that an icon is added to home screen and in display mode, you can NOT see the top URL address bar, nor the Safari options bar on the bottom then the SMS: will fail. If you just open the address in Safari, but don't save the file, then it will work great.
Again, when I'm in Apple Web Application mode, the SMS link fails.
One hack... open the site via Safari mobile browser on the iphone. Save the site to Home Page. Verify the Icon is on the mobile phone. Go to Settings --> Safari --> Advanced --> Website Data, then Delete the site by sliding the content left. Cache storage is clean, but the Icon remains on the mobile screen. Use the Icon to aid in login, but don't save the site again. Note the URL line is visible. SMS will work.
Still testing here...
I tried to build a simple example to show the issue. I was totally unable to get the sample to fail with the error messages above. For reference the test site is here. The test source code is here.
I'm suspecting that the issue revolves around the fact that the two sites in question are both located at a subdomain site. (mywebapp.appspot.com) When the manifest includes all "valid" content the site does appear as a ios Apple Web app without visible URL line... but whenever I'm in that mode, SMS links are a total fail.
With that said, you can control the storage mode via <meta name="apple-mobile-web-app-capable" content="yes"> .
During my testing, I also noticed that whenever the manifest.json file contains // comment marks anywhere the file is ignored by Safari. Normally // comments are not allowed in a .json file, but according the MSN source, they are fine in a manifest.json file.
The choice is
a bit ugly and functional, or
pretty and non-functional
Currently I'm running <meta name="apple-mobile-web-app-capable" content="no">... I get the advantage of a custom icon on the home screen, even though the web app is still obviously inside a mobile browser with top/bottom info lines visible, sigh.
I suspect this must be intentional on Apples part but I will ask anyway because it works from both mobile and desktop safari.
I create a simple .vcf contact from inside my web app and try to download (aka export) it.
This creates a .vcf file in desktop Safari that is actually downloaded where the user actually has to click that to get it into contacts. And in the mobile safari version (without saving to home screen), the exact same code will pop up a warning screen mobile .vcf warning which at least gives the user the opportunity to import the .vcf into contacts.
Admittedly neither the desktop or mobile safari use case it a good user experience but at least they work.
Whereas, the exact same code saved as a homescreen mobile app simply fails without error on an iphone (i.e
)
I have tried multiple ways to export from the app (most of which work from safari mobile or desktop browsers if NOT web app capable)
as a blob from base64 text/vcard
as base64 text/vcard
using window.open(vcftxt); // where vcftext is base64 text/vcard
using location.href = vcftxt; // where vcftext is base64 text/vcard
using an a tag with download= and href= vcftxt url
All the above work..just not in a homescreen app that appears native
code example (run on iphone safari...not tested on android)
https://www.airbridgelabs.com/s/0/app3.html?sd=100 - Click on contacts logo at the bottom when this page opens in safari and you will see the warning which still allows the user to open the .vcf in contacts
https://www.airbridgelabs.com/s/0/app3.html?sd=100&tm2=100 - This will walk you thru saving to home screen or you can simply save to home screen manually without the tm2 parm. click on the contacts logo at the bottom when this page opens in safari and you will see nothing. Safari developer remote console shows no errors or warnings...simply does not work.
I figure I can probably pass the created .vcf to a page on my server which in turn opens the .vcf which will likely then export it to mobile contacts..but that is a lame solution which still requires the user to be online to save an embedded contact.
And please don't use the argument that this is about security. If it was about security then you wouldn't be allowed to do the exact same thing from a desktop page, or mobile safari page or hybrid native app...and you can. This looks like Apple simply reducing the value of mobile web apps that look native.
What I am looking for is an offline work around to simply save a mobile contact already coded into the mobile web app capable content the user intentionally created.
I want to redirect the user to m.domainname.com on his mobile browser. I want to use the existing website but redirect to the m.domainname.com.
For that how can i detect the user is on mobile or desktop.
And how can i redirect the mobile version of same site.
using media screen i can create the seprate displays for mobile divices
using bootstrap i can create the responsive website. but when its on mobile browser i want to redirect the mobile version like m.domainname.com
How can i do this?
And my website is in django.
You can use something like this: https://github.com/gregmuellegger/django-mobile
The idea is to detect mobile device in middleware (https://docs.djangoproject.com/en/dev/topics/http/middleware/).
So, if middleware detects that request going from mobile device, and user requested the normal version of the site, you can redirect him to mobile version of the site.
I am working on a site that has a mobile site: http://www.exchequersolutions.co.uk/m/ I am trying to create a link to the desktop site with out much luck.
When the user clicks on a link I want them to be taken to the desktop site.
The link in the anchor tag is:
<p><a href="http://www.exchequersolutions.co.uk/contractors/cis-self-employed/cis-form/" target="_blank" class="cis_register" >Register Online</a></p>
Does anybody know how or even if this is possible?
Is not possible.
Every browser implement a function to save a link on OS FileSystem (drag&drop or file > save as ...).
You're stuck in a loop caused by user-agent detection.
It looks like there is device detection on the desktop site that uses the user-agent to identify mobile devices. If you follow a link to the desktop site using a mobile phone, you'll just be sent back to the mobile site.
There are a few different ways you can fix this, but it depends on your site architecture. One way would be to disable the redirect on the desktop site if you include a specific parameter in the query string. Another option would be to set a cookie and use that to disable the redirect.
I am wondering if it is possible to make a link that if tapped on (say in iOS Mail), would open up a specific app (I know that part is possible), AND if the very same link were opened up on a regular computer say in Gmail, it would function as a regular web link.
So essentially, two different links in one, depending on the platform you are on.
Where would I start to get something like this going?
I just did it this morning. You need to have your link in the email go to your website. Then on your website check the user-agent and redirect to the app if the user-agent is for iOS and if it is not iOS show the regular web page.
You can't, because you don't have control on which device email is shown.
Best approach would be to code (css/html) responsive email template and hide first link(for pc) if screen size is < 600px etc.
More on responsive emails:
http://zurb.com/article/1144/a-tutorial-on-responsive-email-templates