Reputation: 3671
I have a Facebook tab I created for a client which displays fine on my end. I have also tested it in Adobe Browser Lab and it displays correctly on all major browsers. The link is here:
When my clients goes to see the page I've made for them, they get no output of content. Here's a screenshot they sent me (nevermind that they highlighted everything, you can see that there is no output):
The SSL and non-SSL versions both work. The Sandbox mode is disabled. I'm not sure what the next step is to troubleshoot this. I had them go to the site that the tab is hosted on which is:
http://www.miller-media.com/sites/lambs/videos.html
This displays fine to them which is odd to me so it has something to do with Facebook displaying it.
Thanks for the help!
Client cleared the cache on the browser and then went to the link and it displayed fine when they were logged out of Facebook. As soon as they logged back in, the tab stopped displaying for them. I've got it narrowed down it being an issue with their actual account being able to view tabs (from what I gather). Are there settings that allow people to view or not view tabs? I can't seem to find them.
Ok, so they still can't view the tab. They gave me their login and I went in and looked at the iFrame app on my computer through their account and it displayed correctly. So it's not an issue with their account and it's not an issue with caching. I've had several people check the iFrame and it works fine (in fact, nobody else is having this problem). This problem persists with tabs I built them. I'm currently having them check the version of Google Chrome they are using (I don't know if this would affect it at all). Any other ideas?
I just went into 'Edit Page' from the main admin menu and clicked on 'Apps' on the left side. I found the problem apps and clicked 'Link to this Tab' and I was given this message "Some content in this message has been reported as abusive by Facebook users." There is no abusive content on these tabs. Is there a reason this would happen? Is it a glitch?
Upvotes: 0
Views: 456
Reputation: 43816
This could easily be related to this (presumably temporary) bug: https://developers.facebook.com/bugs/514963005198830
If your client uses the 'Log in as <page>
' functionality it's almost certainly due to that bug
Otherwise: if your app is actually receiving a request when the client attempts to load it you should be able to see if there's something strange about the request, or if it's failing before facebook makes the POST request to your server
Upvotes: 1