Ken Hood

Everything is changing in the Facebook Bug world. The famous (and frustrating) Bugzilla is finally being retired. Here's the NEW WAY to report, browse and follow bugs:
http://developers.facebook.com/blog/post/559/ 

Developers are reporting that Facebook iframe app autoresize is not working. We've seen this bug before, and eventually it was corrected. If your custom app is not resizing (gets scroll bars or cut off at the bottom), please be patient. Facebook has acknowledged the bug and has assigned it as bug 17577. However, I just tested several apps on client pages and I don't see the resizing issue. It's possible that's because I found a javascript tweek the last time we saw this bug (yep- second time around on this bug). So fingers crossed that the "fix" doesn't break something else. Happy coding.

Facebook Pages are not allowing some admins to reorder the tabs on the left side of the page. If you are a developer, please go vote the bug up at http://bugs.developers.facebook.net/show_bug.cgi?id=16712

And someone please let me know if a duplicate exists... I will close mine.

Some are reporting that we are unable to reorder the tabs on Facebook Pages. I have experienced the same today. If anyone has a bug open on Facebook Bug Tracker, please let me know. In the meantime, I will search for a bit more to see if it is already reported.

Well thanks to a good hearted soul on Twitter, Aaron Adams, I now know that the bug is Bug 16211. We shall see which bug Facebook keeps open 16211 or 16337. Hmmm.

Anyway... a genius "duct tape and rubber band" developer has creatively enginerred a workaround that he posted in Bug 16211 that I'm going to try tomorrow if Facebook has not fixed this bug by then. Whew... I can relax for the evening.  :)

Well, that's our best guess anyway (actually the guess of better and brighter folks). Here's the bug number that I *think* may be the one to vote up the ladder: Bug 16337. If I'm wrong, someone please correct me and tell me where the correct bug is.

To all of my retail clients... this does *not* affect our ability to setup our existing custom apps for your pages... so keep telling your friends about our cool tabs. We can still set these up. But unfortunately, for the moment, we're unable to setup a new Earthquake app as well as a new DM app we were working on.

It seems that other developers out there are experiencing the same problem, so it's a genuine problem. We'll keep you posted.

Has anyone else had a problem today setting up a new Facebook iframe app? It seems that we are missing two fields of information in the Facebook Integration section. I'll open a bug if anyone can validate the same problem; missing "Canvas Type" and "Page Tab Type" which seems to have wrecked the loading of the app after it has been installed on a page.

Bug 16102: Just when you thought it was safe to go out out night, and the dust had settled on major bugs, Bug 16102 - ALL iframe tabs are not loading sneaked in. We noticed this while at our daughter's orchestral concert last night. Fortunately, the orchestra and the guest violinist were so incredible, we ignored the bug until intermission.

When we read how widespread and upsetting this was to the "big advertisers" and we realized that major players on Facebook were threatening to pull their advertising... we grinned and knew that Facebook would handle this quickly. This morning we can see that all of the iframe tabs we checked were functioning normally... but the bug is still open, so we assume that there are still some underlying problems afoot. We'll keep you posted.

This bug meant that even though I could create a new custom tab for you, it could only be seen *if* you were logged into Facebook. If you were *not* logged into Facebook, you would get a blank page. Not cool. But it's fixed... yeah. So I can get to work on custom Facebook Page solutions again for insurance agents. I'm working on new tabs and forms that are better than ever! So tuned!

If you already upgraded your Facebook Page, some FBML Custom Tabs (yes, FBML will eventually be phased out by the end of 2011) were incorrectly resized. This has been recently "fixed" by Facebook. That said, they are saying that *if* you still see a glitch on one of your custom FBML tabs, you need to set the body stylle (css) to "margin:0px;padding:0px"

I have checked about a dozen of my clients' pages (I have over 100 for whom I have built custom FBML tabs)... and so far... the "Facebook Fix" seems to work. That said, here is the blog comment by a Facebook staffer (Product Marketing Manager) Thursday, Feb 10, 2011 at 6:11pm:

FBML page tabs should be 520px. In iframe Page there is a bug that makes iframe 512px by default. You can work around this by setting the style of your body tag to style="margin:0px;padding:0px". Fix coming soon.