Facebook mobile workaround no longer working - facebook

Until today, I was able to add ?ref=ts to a Facebook tab url & it would be mobile-friendly.
Not today. Has anyone else experienced this? Is there a workaround to the workaround?
Link for example: https://www.facebook.com/microartssandbox2015/app/924049424328019/?ref=ts
Works fine on desktop.
However, on mobile, I get:
The page you requested cannot be display right now ...

This has never really worked for me. The general (and well known) workaround is to use an external website and redirect to the Page on desktop. On mobile, you just stay on the external website.

Related

Facebook Plugin not showing on my desktop or mobile, but appears fine on another desktop

I've been using the Facebook Plugin for years, on dozens of websites, but all of a sudden, I can only see the page's facebook header, the actual feed appears only as a spinning icon. This is on my desktop and mobile device, feed is at the bottom of the page. https://saltydogfestival.com
screenshot_mobile
However, my co-worker in the desk across from me tried it on his desktop and laptop and the feed loads just fine.
I'm not a page admin for this particular feed.
I have this plugin for other facebook pages, for which I AM an Admin, and those don't show up for me, either. I've tried using Chrome and Edge.
I'm knocking my head against the wall with this.... or maybe it's something so simple that I'm not seeing it... Suggestions??? Please save what's left of my sanity!
I think this issue has affected many sites including mine. I used a third party plugin recently that's said to no affect page speed. It's called "Buttonizer - Smart Floating Action Button" you can add a FB messenger button also and add call to action and any they button as well. I have disabled the Facebook chat one for now. If you can update me if it's now work for you that would be great as I'm in the same boat. Email mtgusto#outlook.com
Edited - bug seems resolved
This is what worked for me:
Go to Facebook Developers - Page Plugin and configure the 'widget' with desired params.
As you change the parameters the preview should update & show. If it doesn't, try signing out.
Click "Get Code" beneath the preview. I used the JavaScript SDK method.
Copy & paste the first piece of code after the < body > tag.
Copy & paste the second piece of code where the box should appear.
Previous answer - leaving here for posterity / reference
It seems to be an issue with Facebook that occurs when the visitor is signed in to Facebook. Try viewing the page in a private window or reload after you have signed out of Facebook to see if it loads when you are not signed in.
There's more information on a Facebook Developers bug report, which was just marked as closed 8/26, although it still appears to be happening: https://developers.facebook.com/support/bugs/584988619248795/
This other community thread has a work-around - look for Dave's comment: https://developers.facebook.com/community/threads/1018223139108570/

Facebook showing page not found when sharing link

I'm sharing content from a website and every time I paste the link into Facebook it says 'page not found'.
Sometimes it works when I manually add the 'www.' in front of the URL in the address bar.
EXAMPLE
Shows page not found:
http://roundreviews.co.uk/reviews/speakers/native-union-monocle-speaker/
Works when you manually place www. in front:
www.roundreviews.co.uk/reviews/speakers/native-union-monocle-speaker/
I honestly have no I idea why it's doing this, any thoughts on how it can be fixed on the web side?
Also...
I have tried with the link below with both the www. and without yet it doesn't work with either of them, this is all very strange. This is the only link I have tried and it doesn't work with both:
www.roundreviews.co.uk/microphones/spark-digital-microphone/
Any help is much appreciated, thanks.
For me what it worked was to access the Facebook Debugger, as Goose said.
I saw that the scrape was about 12 hours ago, looks like it fetches the first time and saves it as caché or whatsoever...
What it worked for me is to debug the url, then click "fetch new scrape information" after the previous information has been shown.
Hope it works!
For those running across this today, you might find that you also need to verify your domain and link it to your page.
To do this you need to
Set up a Facebook Business Account
Add your page to the business account
Verify your domain (using DNS TXT or adding a page facebook gives you)
Under domains, connect your page as an asset of that domain

Facebook Like box does not work with Google Chrome

The Facebook Like box for my webpage does not show with Google Chrome, but shows with IE (not sure about others like firefox). I am using the IFrame code supplied by Facebook. I've tried adding http:// to the Facebook iFrame code... I checked my FB settings (age is 13+, no geographic restrictions) I have read on here that others have had a similar problem, but no answer. I also have the same problem with my other websites that have the like box embedded. Is this a Facebook or Google error? Or did I miss something? Thanks!
http://birdofthehand.com/BotHF_News.htm
(the like box should be under the text that reads "the farm stand is closed")
I've found out that it was my recent update of Avast virus scanner that caused the problem. I said yes to installation of an online scanner.
I checked Google Chromes extension, deleted this extension, and now the like box is loading again.
Erling
Denmark
For me it was the DISCONNECT Chrome extension that was causing the problem.
So anyway, usually it's an extension causing this issue!

Endless loop in a Facebook game with Firefox

I have a game in Facebook and suddenly a new problem came out. In Chrome, Safari, Opera and Internet Explorer work fine. In Firefox the Facebook page loads good but when the game iframe starts loading, it gets a points that automatically reload the whole page. I can not understand what's happening. Anyone could know the issue?
You need to either accept third party cookies or locate the one cookie it needs to load (seems to be the developers's own website usually - look into the list of cookies currently stored on your computer in ff options) and whitelist(allow) that.
Since that answer is nowhere on the net and I just spent one hour trying to figure it out to fix the same problem I'm putting it here in the hope it'll help.
Well, it is good know problem for me, about half year ago I got the same also with Firefox. In my app real problem was that, firefox with his AJAX action, lost somewhere access token from parent window/frame...
My advice: try to stick access token to AJAX's request too.
Edit in response to comment:
Unfortunatelly, now I can't see any token in url into my app frame... but what I did then was something like that: (using jQuery):
$.get("http://mydomain/getInfo?id=12345 + '&' + (location.href.split('?'))[1])
where location.href.split('?'))[1] add session/access token to my intern AJAX request.
Anyway, if application works fine few days ago, check official facebook dev forum, there is often some cause on facebook side...

Error when using mailto: link in Mobile Safari in app-capable mode

I've got a form in a web page with an action that is "mailto:email" (where email is a real email address). When I load this page in Mobile Safari in regular mode (ie, not launched from home screen with app-capable mode), this works fine - after I submit the form, the email app comes up. However, when I'm in app-capable mode and have launched from the home screen (so, no Safari chrome), and submit the form I get the error "URL can't be shown". However, a regular mailto: link (ie, not in a form) does work when in app-capable mode.
Has anyone else noticed this? Any workarounds? Are forms disallowed in app-capable mode?
Thanks,
Elisabeth
This accurately describes the issue. There is nothing wrong with the mailto link, the mailto link fails to load. Often the webapp crashes.
The funny thing is that tel: link for telephone numbers work fine.
window.location.replace does in-fact work. Thanks!
Here is the jQuery to fix this automatically...
$('a[href^=mailto]').click(function (event) {
event.preventDefault();
window.location.replace = $(this).attr('href');
return false;
});
I think I've figured this out. I noticed when in app-capable mode, any http link will take you out of the app and launch a separate mobile safari window, take you to the page and show the Safari chrome. Makes sense (typically one wouldn't link to anything from an "all in one" app-capable web app. I noticed this because I implemented a 4 page app with my own "tab bar" at the bottom and was linking amongst the .html files with plain http links in the a element. When I replace this with a javascript function to load the pages using document.location.replace this doesn't happen.
So, on the form - I think what must be happening is that because I'm using a scheme (in this case, mailto:) somehow the browser is needed in "regular mode" to interpret the scheme and do the right thing by launching the email app and this clearly doesn't work when submitting a form. I haven't yet found anything in the Apple documentation specifically about this, so if anyone knows the technical details, please do post!
UPDATE: I did find that I can access a server side script using a form in web-app mode, so I'm still curious about the mailto: issue, if anyone has an answer.
Thanks,
Elisabeth
I am having the exact same issue with mailto links not working in the web capable mode. I just got done submitting a bug report to Apple. Let's see what happens, meanwhile I found another dev. platform for web apps that works in web capable mode and mailto links work, but it is funny how it works in this even--it is not as fluid as it is in Safari. Because even in this new web dev tool that I found, it closes your app and launches mail client, which is lame. In Safari it just slides in a mail window that slides back out if you hit cancel or send--it doesn't actually close your app.
Here is a workaround that does not depend on JQuery:
aTmp = document.createElement("a");
aTmp.href="mailto:example#example.com?subject=Test&body=Hello.";
aTmp.click();
Update: To run this code from a bookmarklet you have to wait about 1000 ms before the bookmarks bezel is closed and the browser is ready to respond. I realized this by wrapping the code in a setTimeout function.