The Google Checkout Mobile website says that "once you've integrated Google Checkout with your website, there's no additional work required to allow customers to buy from you using their mobile devices", but I'm not seeing this happening on either iOS or Android devices I'm testing. The desktop site comes up, which is workable, but not a very good UI on the small screen.
Since there's "no work required", I'm not quite sure how to start to debug this. Ideas?
I took some screenshots of what it looks like iOS 6 and Android ICS.
According to the support forums, Google Checkout for Mobile devices is just a big fat phony.
I'm just going to go out on a limb and post an answer because I noticed in your header link that there was no User-Agent set. The User-Agent server variable is often used to detect if the user is coming from a mobile browser or not. Here is Google's discussion about Mobile Redirects. So, my suggestion would be to try and set the User-Agent in your server-side code prior to your redirect. The whole workflow would be like this:
Detect the user's current User-Agent variable. Here is a PHP example: $_SERVER['HTTP_USER_AGENT'] and store this variable for later use
Receive the URL from Google Checkout
Prior to your redirect, set the User-Agent. This time, it's a cURL example:
curl_setopt($ch,CURLOPT_USERAGENT,$theUserAgentYouDetected); where $ch is the cURL instance. Here is a normal PHP example to set the user agent: $httpRequest->setHeaders(array('User-Agent' => $theUserAgentYouDetected);
Make your normal redirect
I hope this helps
Related
I use osm in my AngularJS app and in Google Chrome browser I get the following messages
So I do not have access (any more) to the tiles. Three days ago it worked fine. If I open the application in Firefox everything is fine and works.
Is this an adjustment in Google Chrome or how I can find out what I have to do in order to get it work with Google Chrome anymore.
Not sure if this will help, but from PINTOSTACK, in
https://help.openstreetmap.org/questions/83887/unable-to-download-tiles-403-forbidden
"Maybe this will help someone else, for those using leaflet, we fixed it by changing http to https on the tileLayer png. Seems to work on localhost in Chrome & Edge."
I made the change and this worked for me.
You are not adhering to the tile usage policy. That's why your access denied message links to that policy.
OSM became stricter in enforcing the policy recently.
Could be related to another provider that slashed It's free tier by 99% recently and therefore users flocking to OSM.
As the tile usage policy stats: "OpenStreetMap data is free for everyone to use. Our tile servers are not."
(see: https://operations.osmfoundation.org/policies/tiles/ )
So please follow that policy closely if you use OSM for light use. For use in a business context or an app you shouldn't use those tile servers by the OSMF anyway (see the usage policy that asks you not to hardcode the tile.openstreetmap.org URL into an app).
Alternatives can be found here: https://wiki.openstreetmap.org/wiki/Tile_servers
If your angular application is producing only light use and not used for business contexts, check your dev tools in Chrome about the User-Agent and referrer your angular app is sending.
Is there a way to tell if a mobile page you've downloaded is just a desktop page modified with media queries, or is a separate page designed specifically for mobile? I'd like to go through a list of the "20 Best Mobile Pages" and see what percent were designed specially for mobile.
Let me express my understanding on your task:
You want to check whether one webpage, e.g. https://www.google.com, is designed for both mobile device and desktop computer(it means the two types visit could cause server deliver different webpage), or just for mobile device or just for desktop.
If my understanding is right, the following is my answer:
You could change the "user agent" in your http request, then analyze whether you could get the same or different content from the same URL. About the "user agent", more explanation is here:
https://www.thoughtco.com/detecting-hits-from-mobile-devices-3469093
After you get the contents from different "user agent" settings in your http requests, then if the mobile device's type "user agent" content is different from the desktop's type "user agent" content, then you could assume that URL page is specially designed for a mobile device.
But because there is no special international standard to tell the client whether the content is for mobile or for desktop computer, so it's your job to make this decision after you get the same HTML content from both mobile device "user agent" and desktop "user agent" settings.
Google has a test specifically for this problem, it has API using REST, it can be used with Go,Java, Javascript, PHP, Python and Ruby:
https://developers.google.com/webmaster-tools/search-console-api/
I hope this helps.
Go on the site on desktop, then use Chrome's inspect element to test a mobile sized browser. Then go on your phone and go to the site. If the results are different, then it was designed for mobile, if not then the website was just built to be responsive.
We recently had a mobile site built which was great but when we send out our html emails I'm having to use media queries on the links to send customers to the desktop site or mobile site as the URLs are different Eg. m.mobilesite.com and www.desktopsite.com.
I'd like to use something like 'detectmobilebrowsers.com' so I can do away with the media queries and have one link which is built up of both the mobile and desktop links. The setup advice on this site is not very helpful.
Does anybody know how to do this?
Personally, I don't like the sound of that. You cannot guarantee that the mail/webmail client will be able to support "responsive links", regardless of the device that the user is viewing it on. Hence, you could very well be pointing users to the wrong device specific site.
What I would do, is point all of your email links to the main site version. At that point, you should have some form of device detection in place on your server. Your site logic should be able to forward the user on to the correct site specific page (e.g. mobile visitor sent to mobile version of same page, desktop user not redirected).
If you don't any redirection logic in place (you really should, read this), basically this is what you're looking to achieve:
http://www.9xb.com/wordpress/wp-content/uploads/2012/08/mobile-deployment-small.png
If you're not following the rules laid out by Google regarding redirects and canonical link tags, you may find yourself in trouble at some point.
If this is all a bit beyond your technical ability, I'd suggest you speak with whoever built your mobile site as this isn't for the faint hearted.
I want my website to redirect mobile users from mydomain.com to m.mydomain.com (unless they have specifically asked to see the non-mobile site).
I was doing this in my application using WURFL, but I want to enable page caching. If page caching is on, the application will never be reached to know to redirect the mobile user, and so I need nginx to do this.
Apache has modules such as Apache Mobile Filter that make use of WURFL.
Is there any good way to detect a mobile browser in nginx? I'd rather not just come up with a user-agent regex since there are so many different mobile user agents that are always changing.
I don't believe there is a dedicated nginx core or third-party module for this. Since any module would simply test the user-agent anyway, I can't imagine anyone creating a module for this specific purpose.
However, it should be relatively simple to set-up a check on the user-agent and redirect. You may find it preferable to check for Gecko/IE/webkit/opera explicitly and redirect everything else to your mobile site - that way you're maintaining a smaller ua regex, plus you'd be catering for the mobile safari (iPhone/iPod Touch) by keeping them on your main website. Its then a simple step to special-case for that browser should you wish to.
Furthermore, you should be able to check cookie contents in your nginx config to decide whether to redirect based on the user-agent's preferences.
I am planning on making a WAP page to provide a software.
Now i need to find out what mobile phone model the client who logs into my webpage is using so that i can redirect him/her to the appropriate download link.
This is similar to what opera does on their opera mini site. When you log in it finds out your model and sends you to the link
How can i add this to my site.
There are a number of solutions for determining mobile device, based on the UserAgent making the request. (Some solutions use other factors as well.)
Try looking at:
WURFL
MDBF
DeviceAtlas
DetectRight
Volantis
MobileAware
Movila
UAProf
The technology you are using to create your pages will also affect which of the above is the best solution for you.
A great website with some tutorials is mobiforge.com (the people behind device atlas), also plenty of true open source software at wurfl