yup.. realized my error.. changed the url as well with the slash..didn't change anything...

should the url contain the directory where piwigo is?

http://www.seeberg.com/piwigo/ or
http://www.seeberg.com/

it is currently
http://www.seeberg.com/piwigo/

Last edited by phantomracer (2013-03-07 02:01:05)

This happens when PHP error reporting is set to the "notice" level. You can either change the error level, or edit the auth.php file in the oAuth plugin folder the following way:

change

if ($provider == 'OpenID')
  {
    $params['openid_identifier'] = $_GET['openid_identifier'];
  }

to

if ($provider == 'OpenID')
  {
    $params['openid_identifier'] = $_GET['openid_identifier'];
  } else {
    $params = array();
  }

Oops, sorry. I just realized that - Piwigo doesn't notify me of the new version either. I shall read more closely next time :)

I had issues with Yahoo, the most important is step 6

Once the application is registered update the permissions : set Contacts as Read and Social Directory as Read Public

Hello,
i have the same message, error code 0..
should i have to change the something in the  notice code list ? as i saw in another thread ? :
This happens when PHP error reporting is set to the "notice" level. You can either change the error level, or edit the auth.php file in the oAuth plugin folder the following way:

change
Code:

if ($provider == 'OpenID')
  {
    $params['openid_identifier'] = $_GET['openid_identifier'];
  }
to
Code:

if ($provider == 'OpenID')
  {
    $params['openid_identifier'] = $_GET['openid_identifier'];
  } else {
    $params = array();
  }


Thanks for your help

the empty openid_identifier is NOT the cause, as Facebook is not a OpenId provider

I think the only cause is that Facebook can't contact your host (or the reverse) to check the authentification

Well I knew my problem wasn't just me. 
Here's the bug fix for the Facebook problem I was having.  It's all to do with the CSRF checks in the HybridAuth library + the URL generated by Piwigo's get_absolute_root_url() function.

The problem:
The URL https://example.com:443/test is considered different to https://example.com/test even though they are the same website; the only difference being the URL port number.

The HybridAuth library that communicates with Facebook fails with a "CSRF state token does not match one provided" error even when authentication is actually successful.  This means you get an "Authentication cancelled" message even if it's a CSRF problem, not a Facebook problem.

The cause:
Under Piwigo include/functions_url.inc.php the get_absolute_root_url() function doesn't remove the default port number of 443 for HTTPS domains.  The oAuth plugin currently uses this Piwigo to generate the Facbook callback URLs.

Solution:
Edit the Piwigo functions_url.inc.php file and change the line:

if ($_SERVER['SERVER_PORT'] != 80)

to

if ($_SERVER['SERVER_PORT'] != 80 && $_SERVER['SERVER_PORT'] != 443)

Another solution is to modify the plugin/oAuth/main.inc.php file to use another function to define OAUTH_PUBLIC (this has been my approach). 
This is a neater fix and won't break on Piwigo updates - but I'll leave this to the oAuth maintainer.

The best thing I did to finding the cause was fixing the annoying plugin/oAuth/auth.php error message 5 of "Authentication cancelled"!  I highly recommend you change this line:

$template->assign('ERROR', l10n('Authentication cancelled')); break;

to:

$template->assign('ERROR', l10n($e->getMessage())); break;

No more Facebook authentication problems when using SSL. *sighs with relief*
David