Numerous Facebook page owners tell us that page
tab images are randomly changing to another page's custom tab image.
This is happening without any interaction. After a tab image is set,
sometimes when you go back to it later the image that appears is
different.
Here is what we believe is happening. There appears to be a limit of 10,000 tab images for an app. When a tab image gets uploaded a number between 0 and 9999 gets assigned to the tab image creating a url like this:
http://photos-c.ak.fbcdn.net/photos-ak-snc1/v85005/64/208195102528120/
The last part 6562 is what seems to be randomly allocated and limited from 0 to 9999. For apps with large numbers of users like the Woobox, Static Iframe Tab, users quickly fill up the allotted 10000 slots and when new tab images are uploaded, it overrides an existing tab image which then changes the image on the original page.
The only solution we've come up with is to ask users to setup their own custom apps hosted on our system. When they setup their own apps, only they are uploading tab images for that app reducing the chance of this happening.
You can reproduce this issue by following these steps
| Steps to Reproduce: | Change the tab image for an app with lots of users such as 208195102528120 Watch as one of the 10000 slots gets taken that was previously allocated to another page tab image. To see this in action with the CDN cache, take the image url and load it like: http://photos-c.ak.fbcdn.net/photos-ak-snc1/v85005/64/208195102528120/ then load it again with ?uncache at the end to have the CDN recache it: http://photos-c.ak.fbcdn.net/photos-ak-snc1/v85005/64/208195102528120/ You'll see different images, the old one and the new one. | |
|---|---|---|
| Expected Behavior: | Each image uploaded needs it's own unique identifier to not override previously uploaded images. | |
|---|---|---|
| Actual Behavior: | Each image uploaded runs the risk of overwriting another application users tab image. |
|---|
(Source : Facebook Developers)
No comments:
Post a Comment