Error related to Facebook Locales

Same...

This error occurs only when cache is cleared.

I solved this problem with the help of Devel Module. If you go to the code line typed in the message, you insert a Devel debug instruction (dpm($result);), under the request sentence ($result = drupal_http_request("https://www.facebook.com/translations/FacebookLocales.xml");), and you clear the cache, you'll see the detailed error: Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?

Then, you can enable that extension in your php.ini (extension=php_openssl.dll).

Hope this helps.

I have a similar error
Error opening socket ssl://www.facebook.com:443
but I believe take active openssl
my phpinfo():

openssl
OpenSSL support enabled
OpenSSL Library Version OpenSSL 1.0.1e 11 Feb 2013
OpenSSL Header Version OpenSSL 1.0.1e 11 Feb 2013

this occurs in a development server, I hope that when I go to production not have problems

seisunos thanks for the tip to debug

Sorry to reopen this one..but I have this error and I have tried all step that I found on all issues...can anybody tell me how to solve the problem?

Hi!
Solution at #2 worked for me. Thanks!

$ drush -y cc all
Invalid argument supplied for foreach() socialmedia.widgets.inc:754

OpenSSL is present.

Affected line:

foreach ($xml->locale as $line) {

Context:

function _socialmedia_widgets_get_facebook_locales() {
  $fb_locale = array();
  $cache = cache_get('socialmedia_facebook_locales');
  if (empty($cache->data)) {
    $result = drupal_http_request("https://www.facebook.com/translations/FacebookLocales.xml");
    $xml = simplexml_load_string($result->data);
    foreach ($xml->locale as $line) {

Testing:

$ drush ev 'print_r(drupal_http_request("https://www.facebook.com/translations/FacebookLocales.xml"));'
stdClass Object
(
    [code] => 0
    [error] => Error opening socket ssl://www.facebook.com:443

$ curl -s https://www.facebook.com/translations/FacebookLocales.xml | head
<?xml version='1.0'?>
<locales>
<locale>
<englishName>Afrikaans</englishName>

Sometimes it can be related to transparent corporate proxy so some certificates needs to be imported, or firewall (which blocks Facebook).

But in this case, curl works, so it's something else.

So still code needs to implement some failing scenario when the host is not reachable.

The attached patch checks if there are no errors in the response from Facebook before trying to cache the locale. It won't fix any issues with the call to Facebook but it will suppress the Undefined property related notices and warnings.

This was fixed in a recent issue.

#2556779: Facebook Locales XML feed broken

While just checking for the data works, I'm going to assume it isn't coming back. There was a JSON version on Github that I linked to to use that as well, so at least there is some sort of fallback available.