=>> Watch the Video of Facebook Error on Page Here! <<=
Facebook error on page makes the user stress, usually. As you know, Facebook users love to get indignant. If it’s not another unsettling redesign on the social network of choice, then they’re launching Facebook groups to protest another privacy infringement one or several civil liberties advocacies are mad about. And now, you can’t block Facebook founder, CEO and everybody’s most hated self-made ka-jillionaire, Mark Zuckerberg from seeing stuff on your profile.
Last Friday, Facebook had acknowledged that they were aware of the problem and working on a fix. Facebook has just released an update for their iPhone app, which should fix the problems. Many Facebook users have reported today that they are receiving a message to download a file called gzip_detect.php. It seems the message is affecting people running Internet Explorer.
=>> Watch the Video of Facebook Error on Page Here! <<=
Facebook’s “block” feature allows you to prevent a specific Facebook user from seeing your profile, or even finding your profile in a user search conducted through Facebook. Attempt to block Zuckerberg and as of this morning, you’ll get a prompt that reads, “General Block failed error: Block failed.” We don’t know what the file is, and the information online does not provide any insight on the nature of the php file. In any case it would be best not to download the file and save yourself from potential trouble.
Either way, you can verify this by going to Zuckerberg’s Facebook profile, scrolling down near the button of the left panel and clicking “Report/Block this person,” then checking “Block this person” and clicking “Submit.” A new Facebook bug appeared after yesterday’s code update, and this time, it appears that all users’ hidden email addresses were exposed for a period of a few hours, before Facebook patched the hole. However, the few hours would still have given spammers plenty of time to comb the site for millions of email addresses.
Facebook hasn’t stated anything regarding this issue, and the latest tweet from them was days ago in August 9th. Some people are not getting this error, like here for example. Each method call to the API may return Facebook error instead of the expected result due to possible bugs in either the application’s code or Facebook’s servers. On this page, you can find all of the potential errors that could be returned, as well as the functions which can return them. In the PHP client, these are thrown as exceptions. If you want to degrade gracefully, you will need to catch them appropriately.