Apparently, Facebook doesn’t like .png images. When I tried to defined a png in the open graph properties “og:image”, the loading icon in the share window goes on for awhile before disappearing entirely. Fix: use a .jpg instead.
As advised on facebook docs: og:image – An image URL which should represent your object within the graph. The image must be at least 50px by 50px and have a maximum aspect ratio of 3:1.
Also, consider using the handy linter utility at http://developers.facebook.com/tools/lint/ to check the meta data of your page.
EA just spent $275 million (and up to $400 million in equity retention and variable cash considerations) to acquire Playfish, the social game company behind Pet Society and Restaurant City, popular games on social networks such as facebook and myspace.
For a comparison, Microsoft paid $375 mil for Rare, a record at that time.
Electronic Arts also bought Maxis (The Sims) for $125 mil and Westwood Studios (Command and Conquer) for $122.5 mil, and Intermix Media, parent company of myspace.com was accquired for $580 mil in cash by Fox’s News Corp.
Read the full article here.
Serious facebook developers would be familiar with this tag. It basically allows you to render fbml outside a fb canvas pages. Now the frustrating bit.
While writing the invite page for my facebook app, I realize I could not render any fbml when the page is in an iframe. If I set the Render Method to canvas it works fine, so the problem wasn’t with the fbml itself. The xd_receiver was also referenced correctly. After a morning of testing I decided to ask Alvin for some of his old code, and it turned out to be exactly the same, which was puzzling since it definitely worked before.
Another few hours of fruitless searching finally led me to a post which provided a simple solution: set the Connect URL to the same url as your Canvas Callback URL. Appears that this requirement was put in place after an update from facebook. They automatically patched the settings in older apps that used xd_receiver so older apps would continue to run properly, but not surprisingly they missed this out in the developers’ wiki.
Since I was developing a native FB app I had skipped the fbConnect settings entirely, my bad. Now I’m posting this here (with hopefully more intuitive keywords) in case someone else is having the same problem.
ps. For general news and updates for the api remember to check http://developers.facebook.com/news.php?tab=updates often.