Hello!
I have boost enabled and installed before month Drupal for Facebook and later deactivated it. But I have so many cached pages in my boost folder with URLs coming from the wall page with many arguments included. For example: lazy-cat_fb_xd_fragment=.html
mypage_cb=f3e29dce81bc09&height=21&page=0%2C3&relation=parent.parent&transport=fragment&type=resize&width=350.html
blog_page=173&fb_canvas_fb_canvas_fb_canvas_destination=blog?page=467&%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F=.html
and so on. When I click on wall link to my site, I am redirected to address:
http://www.facebook.com/l.php?u=http://www.example.com/history-brief&h=5...
So it's added &h=51322 in the end of the address.
I already asked in Boost module forum, but they can't help for now. Do you know if something I can disable in Facebook Apps or Pages to stop receiving this URL arguments?
Thanks in advance!

Comments

Terko’s picture

Terko commented

I forgot to say, that I use only Like buttons and Facebook Like Box (fan page).

Terko’s picture

Terko commented

I've implemented this bug workaround
Just before tag in the template you can paste this code:


<!-- Correct fb_xd_fragment Bug Start --> 
<script> 
document.getElementsByTagName('html')[0].style.display='block';
</script> 
<!-- Correct fb_xd_fragment Bug End -->

Taken from there http://forum.developers.facebook.net/viewtopic.php?pid=232516

Dave Cohen’s picture

Dave Cohen commented

Thanks for keeping us informed.

Is this boost-specific? Any simple way to reproduce?

If it's a common problem, might be worth adding that one line of javascript to fb.js.

Terko’s picture

Terko commented

Just Boost caches the new URLs, so the cache is tripled. If you have Like button and Facebook App configured, you can see in your cache folder all the additional URLs. Instead of having 100 URLS, you can have 300 with all URL arguments passed to the site to process.

Dave Cohen’s picture

Dave Cohen commented

But if you want to keep statistics and know where your users are coming from, that's not a bad thing, right?

Terko’s picture

Terko commented

Yes, maybe it's not bad thing, but this behavior produces many versions of one cache file, and this is something that break the performance that I need from the cache :(

socki’s picture

socki commented

This seems to be a problem with the facebook sdk.

Another potential solution I posted at http://drupal.org/node/1009300

Hope that helps.