Facebook 'Like' XFBML causes page URL to change adding ?fb_xd_fragment to the string: Why. How fix
Facebook 'like' XFBML or it's constituents
xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" as in the standard page leadin:
"<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/">
or the related SDK script - see snippet below; note: I've replaced the app id only here in this query view of that code, not in the actual page code itself - appears to cause IE8 to have conniptions on certain user pcs and now Google offers "http://www.missi.com/missiWebOpening.html?fb_xd_fragment" as search result which is completely wrong.
For some reason that I do not understand, if someone attempts to open "http://www.missi.com/" in IE8, the page initially paints perfectly but, once completed, on some user pcs - but not all - the URL suddenly, inexplicably, changes automatically to "http://www.missi.com/missiWebOpening.html?fb_xd_fragment" and the browser consequently goes completely blank - no underlying code appears when right clicking on this blank page to show its source content - because there is no such page as one related to the "?fb_xd_fragment" on our web server.
Can anyone explain this and, more particularly, how to fix it and how to accommodate the result if someone clicks on this link in a Google Search result so that they will be sent to the correct URL instead of this non-existent 'fragment'? Would also be helpful to know how to remove this erroneous link from Google's search results.
This weirdness happens only when using IE8 only on some, not all, pcs. No problems using Chrome, Firefox or Safari.
xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" as in the standard page leadin:
"<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/">
or the related SDK script - see snippet below; note: I've replaced the app id only here in this query view of that code, not in the actual page code itself - appears to cause IE8 to have conniptions on certain user pcs and now Google offers "http://www.missi.com/missiWebOpening.html?fb_xd_fragment" as search result which is completely wrong.
For some reason that I do not understand, if someone attempts to open "http://www.missi.com/" in IE8, the page initially paints perfectly but, once completed, on some user pcs - but not all - the URL suddenly, inexplicably, changes automatically to "http://www.missi.com/missiWebOpening.html?fb_xd_fragment" and the browser consequently goes completely blank - no underlying code appears when right clicking on this blank page to show its source content - because there is no such page as one related to the "?fb_xd_fragment" on our web server.
Can anyone explain this and, more particularly, how to fix it and how to accommodate the result if someone clicks on this link in a Google Search result so that they will be sent to the correct URL instead of this non-existent 'fragment'? Would also be helpful to know how to remove this erroneous link from Google's search results.
This weirdness happens only when using IE8 only on some, not all, pcs. No problems using Chrome, Firefox or Safari.
<div id="fb-root"></div>
<script type="text/javascript">
window.fbAsyncInit = function() {
FB.init({appId: '99999999999', status: true, cookie: true, xfbml: true});
};
(function() {
var e = document.createElement('script');
e.type = 'text/javascript';
e.async = true;
e.src = document.location.protocol +
'//connect.facebook.net/en_US/all.js';
document.getElementById('fb-root').appendChild(e);
}());
</script>
ASKER
The reply from sam2912 was helpful in that it led me to a page showing that various people have encountered this problem and that Facebook support has not yet provided any specific answer, response or fix.
This "bug" page offers a variety of possible solutions, many of which appear to be incomplete for all who have tried.
I have thus far not attempted to test any of the suggested answers because I do not have time to waste in experimenting to solve a problem that should be solved by Facebook.
So the jury is still out. Meanwhile, I have discontinued using the Like button until a definitive answer comes along.
This "bug" page offers a variety of possible solutions, many of which appear to be incomplete for all who have tried.
I have thus far not attempted to test any of the suggested answers because I do not have time to waste in experimenting to solve a problem that should be solved by Facebook.
So the jury is still out. Meanwhile, I have discontinued using the Like button until a definitive answer comes along.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
xfbml: true
Please see related articles/discussion:
http://bugs.developers.facebook.com/show_bug.cgi?id=9777