I'm using PayPal Payments Advanced with the hosted checkout pages for a mobile site and can't seem to get it to render as a mobile view on my phone. I've followed their documentation but nothing seems to be working:
https://developer.paypal.com/docs/classic/payflow/integration-guide/#hosted-pages-and-mobile-browsers
It clearly says:
PayPal’s hosted checkout pages are mobile optimized for iPhone, iPod and Android devices. This mobile optimized experience is available for all 3 Layout templates A, B and C. In the case of Layouts A and B, PayPal will auto-detect if the checkout page is being viewed from a supported mobile browser and will redirect to the mobile optimized checkout page.
We are using Layout B, which should be mobile friendly according to the above, but it definitely does not look mobile friendly. I've also tried adding TEMPLATE=TEMPLATEB to the POST data that hits this page but that doesn't work either. Here is a screenshot of what it looks like on my LG G4:
As you can see, it doesn't look very mobile-friendly. The thing is, when I click the "Checkout with PayPal" button it does go to a mobile-friendly version of the PayPal login, but I need this page to be mobile-friendly. Does anyone have a clue as to how I can get this to work or is this a limitation with PayPal?
Paypal screen became responsive when we passed SecureToken and SecureTokenId as querystring parameters instead of passing those values as form post.
That is instead of passing in form post.
<html>
<body onload='document.forms["myForm1"].submit()'>
<form id='myForm1' method='POST' action='https://pilot-payflowlink.paypal.com'>
<input type="hidden" name="SECURETOKEN" value="..." />
<input type="hidden" name="SECURETOKENID" value="..." />
</form>
</body>
</html>
We passed those values as querystring parameters.
https://pilot-payflowlink.paypal.com?SECURETOKENID=...&SECURETOKEN=...
Not very sure why PayPal is handling those differently.
Related
My website is a Single Page Application written with AngularJs.
I am trying to add AdSense for some pages. After submitting, my site was rejected because of the following reason: "Insufficient Content".
My question here is: were adSense crawlers able to access and view my website considering that we use escaped_frangment and phantomJs to render the pages? (This works pretty fine for google bots.)
What can I doto make my website approved by adSense?
Thanks in advance.
I've used Prerender successfully in the past. It was a bit of a pain to set up, but works very nicely.
Search engines and social networks are always trying to crawl your
pages, but they only see the javascript tags...
We render your javascript in a browser, save the static HTML, and you
return that to the crawlers!
I am working on a news website, trying to implement amp. We are using Mobile_Detect.php to serve desktop pages to desktop and tablets, and mobile version to mobile phones and that works OK, our pages are mobile friendly according to Google for some time now, no problem.
Now, I started to enter the code for amp pages and encountered a situation I can' resolve. URL for the amp version have .amp at the end. Depending on the user's device, we are generating the page from the database and serving different pages to different devices.
Now, PageSpeed Insights and Mobile-Friendly Test shows that the page is mobile friendly but amp validator is pulling the desktop page, I can see by the source code it prints out, instead of a mobile page. I'm on the desktop, Chrome, but I'd expect it to work with mobile pages.
You can see that here: https://validator.ampproject.org/#url=http%3A%2F%2Fwww.poandpo.com%2Fbusineasdfasdfas-usual%2Fpublic-housadfadf-kong-972016223.amp
I installed Chrome amp extension and it says "AMP available" but when I click on it it also pulls the desktop version of the page and it's blank. I would expect the extension to load the mobile page but it doesn't.
We do have links canonical and amphtml, that's why the extension says there is an amp page.
So, how to tell validator to pull the mobile version of the page? The amp implementation is not done yet and I know there are some things missing, but without a validator is a bit hard to program.
Another interesting things is that when I open "Inspect" in Chrome and toggle to responsive design, it shows the mobile version of the webpage correctly. It also says "Powered by amp" and shows no errors although there are errors because we didn't even implemented all tags.
If anybody has any suggestion how to make amp validator to show the mobile page I'd appreciate that. Thank you.
I had a quick look at your pages but it appears that the amphtml reference but there appears to be a problem in the URL you are generating in the href= field. If you take a close look, the AMP URL is missing a '/'.
Broken: http://www.poandpo.com/business-as-usualmexicans-work-longest-hours-germans-the-least-97201645.amp
Works: http://www.poandpo.com/business-as-usual/mexicans-work-longest-hours-germans-the-least-97201645.amp
I've set up a Buy Now PayPal button on my site and everything works absolutely fine, including the PDT, etc.
However, on the mobile version of my site, the payment page is not at all mobile friendly. When the user clicks/taps "Buy Now", they are redirected to PayPal, but the screen that is displayed is not responsive.
I'm just using the standard code from the Buy Now button generated through PayPal. Am I missing something here?
Thanks in advance.
There are some feature that is not supported on mobile checkout page.
If you use these the checkout page will still be a PC page.
Please refer to the page below:
https://developer.paypal.com/webapps/developer/docs/classic/products/mobile-paypal-payments-standard/#usecases
I'm looking at what's required to develop a web page for the Kik Messenger in-app browser and I'm confused as to how the development workflow is supposed to work.
The API Docs say that "To launch your webpage in Kik simply open the sidebar and type in the URL to your webpage.", which would be fine except for the fact that the "sidebar" no longer exists in the current version of the app and it no longer seems to be possible to enter an arbitrary URL(*).
* EDIT: It looks like you can open an arbitrary URL in the browser by entering it into chat and then tapping on it.
Given these restrictions, how do folks test their web pages with the app? Do you have to just use the Chrome Extension until deployment?
Related question: How do you make Kik aware of your web page? Some of the other questions on this site imply that you have to wait for their web crawler to index it. Is that the case? If so, is exactly how this works documented anywhere? I feel like I've missed a doc link along the way.
In December they removed the NEW Apps tab in the Discovery Section as well as the option to access arbitrary URLs. (as you pointed out) For testing I usually use the Chrome extension or access my testserver via an URL from a chat.
But since the NEW tab is currently removed, it is not very feasible to release new Kik Apps at the moment, since people would only be able to discover your App by using the Search function and getting into top 100 would be very unlikly this way. I contacted Kik if the removal of the NEW tab was a permanent change, to which I got the response that they are currently revamping their platform and new solutions on the way for the stuff they are moving.
So if u are currently working on a Kik App I would recommend waiting with releasing it until possible future updates of the Kik Browser are released.
As for your other question to make the crawler find you app, you simply have to add some Meta tags into your header:
<meta name="description" content="app description">
<link rel="kik-icon" href="your image")">
<link rel="canonical" href="your domain">
<script src="http://cdn.kik.com/kik/2.0.5/kik.js"></script>
I've a mobile version of my site which has a 'Donate via Paypal button' on it which is working fine. It's a button generated from within the paypal account that when clicked brings users to my account and asks them to enter an amount to donate and then either login or pay with CC.
Problem is the Paypal page it brings me to is not mobile optimised. From reading online It appears Paypal only offer the mobile enhanced version if you're using Paypal Mobile express checkout which is far more involved than simply adding a link onto your page.
The system I have now is 100% functional and does everything I want it to, I just want it to switch to the mobile version when you go to Paypal, to be honest it's very surprising Paypal doesn't do this automatically. They should detect a mobile browser and just change the stylesheet or redirect to the mobile-login page.
Is there any way of getting the mobile-styled paypal page without having to jump through the hoops of using the express payment system? I know it's not masively difficult but it is when compared to the really simple version I'm currently using.
After hours messing with Pain Pal I finally figured out the issue. If you use a link generated by PP for donating ON THEIR SITE - ie. You go to Paypal and once there you enter the amount you wish to donate - the it won't style as the mobile site.
However, if you take the amount in on your own site and pass it to Paypal then it will auto change to the mobile site.
Ignore anyone on line (and there are plenty of people who do) telling you that to get the mobile styled site you need to use their mobile express checkout. You do not. At least not in the above scenario.
As stated here the mobile optimisation is not working for "Donate" buttons.
Which command did you use ?
With cmd=_donations its not showing the mobile version. When you use cmd=_xclick its mobile optimised, but then its not a "Donation" Site.