BugsCustom Page tab images are changed after being selected
- Status: Fixed
- Priority: None
- Updated: April 3, 2012 at 1:22pm
Latest response from Facebook
Jeff Bowen
This should now be resolved. Thanks for your patience.
Status changed to Fixed · April 3, 2012 at 1:22pm
Eric Osgood
Sorry for the erroneous status update, it was intended for bugs in a stale state. Please disregard the previous message.
March 27, 2012 at 10:50am
Jeff Bowen
We pushed a fix yesterday that makes this *much* less likely to happen now. We're working on a complete fix that will solve the problem altogether that should hopefully go out this coming Tuesday or the next. If you change your tab image again, it should stick now.
March 21, 2012 at 5:46pm
Jeff Bowen
Thanks for the report. We are looking into this.
Status changed to Assigned · Priority changed to High · March 19, 2012 at 11:04am
We've had numerous Woobox customers 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.
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.
| 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. |
2 people can reproduce this issue by following these steps
Repro