Social Login (Google Login, Facebook Login, Apple Login) [Support Thread]

I've just finished building a plugin that allows logging in with Google, Facebook and Apple.

Google is tested and works perfect, Facebook is pending testing (requires verified business so I'm awaiting for them to verify me), but Apple requires a paid developer account.

Does anyone here have access to Apple Developer Program account and is willing to help me test the module before releasing it? We would need to create an App, get the app ID and Secret, and get the .p8 cert. I'm guessing some users might find it attractive and won't mind paying the $99 per year to allow Apple login, but I'm not one of them... If you're interested in helping test it, please PM me to get access to the plugin.

The plugin will be released as soon as Facebook and Apple are tested, but if there's no response for Apple, I'll just remove the option and keep Google and Facebook.

Plugin now available:
https://github.com/zenexpert/social-login

Detailed step-by-step guide for getting the required credentials available in the wiki page.

Any comments and/or suggestions most welcome.

Thank you for this plugin.

I am experiencing one problem though. I have succesfully setup the Google app and got the two keys. when activating the sign in with Google option an error 500 is genrated. I am using version 2.2.2 on PHP 8.4

--> PHP Fatal error: Uncaught Error: Undefined constant "TEXT_FALLBACK_FIRST_NAME" in /zc_plugins/SocialLogin/v1.0.0/catalog/includes/modules/pages/social_oauth_callback/header_php.php:137
Stack trace:
#0 /index.php(40): require()
#1 {main}
thrown in /zc_plugins/SocialLogin/v1.0.0/catalog/includes/modules/pages/social_oauth_callback/header_php.php on line 137.

Please assist

Thanks,

Kobie

I've noticed the same problem a few days ago and have fixed it, just haven't uploaded the changes. The fix will be included in v1.1.0 (should be available tomorrow).

In the meantime, please edit zc_plugins/SocialLoginv1.0.0catalogincludesmodulespages/social_oauth_callback/header_php.php and add one new line at the top. So, instead of

<?php
declare(strict_types=1);

// Load the bundled Composer autoloader
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';

global $db, $messageStack;

you will have

<?php
declare(strict_types=1);

// Load the bundled Composer autoloader
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';
require DIR_WS_MODULES . zen_get_module_directory('require_languages.php');

global $db, $messageStack;

This should resolve it.

Thank you, I can confirm that the login using Google is now working.

Thanks for the quick response.

Kobie

balihr:

...

<?php
...
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';
...

you will have

<?php
...
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';
...

i am very confused...

this does not seem to be the gold standard?

best.

carlwhat:

balihr:

...

<?php
...
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';
...

you will have

<?php
...
require_once dirname(__DIR__, 3) . '/classes/vendor/autoload.php';
...

i am very confused...

this does not seem to be the gold standard?

best.

Haha, no it's not, but it's a much much better approach. You see, traversing the file system could be a problem if ZC allowed files from different versions of a plugin to be used congruently; but it does not. the use of __DIR__ exists in many packaged libraries, including composer, apimatic, symfony, etc. the idea of hitting the db multiple times when you know where you want to go seems ludicrous. I mean, at least that's what a wise guy told me on github. You might've seen him, he goes by proseLA. 😛

Now, here's what happened. This plugin has been "cooking" for quite some time, I had started it early this year. I remember you suggesting this approach somewhere else (can't remember where exactly), and I had applied it at some point and it was great. Then, when I was doing the ajax cart plugin, I figured I'd go for the "golden standard" so I don't get scolded (again!) when I release it. You were right and you've definitely proven your point, so from now on, I'll be back to using "your" method as I do agree it's better and cleaner. The ajax cart plugin is also getting a push today with some of your ideas included - stay tuned.

And, honestly, this is why I love this community - a friendly nudge in the right direction makes things better for everyone.

kobie:

Thank you, I can confirm that the login using Google is now working.

Thanks for the quick response.

Kobie

Thanks for the update, glad to hear it's all good now.