Support

If you are on Joomla 3: There was no universal method for adding buttons to Joomla's login forms. While we came up with a solution which works most of the time, it won't work when the username and password fields are in a different DOM container than the login button itself. In this case, you can of course make your own template overrides for your login module and/or login page, adding SocialLogin buttons manually (see https://github.com/akeeba/sociallogin/wiki/Integrating-with-template-overrides).

If you are on Joomla 4: Joomla 4.0 and later does come with a universal, official method for adding buttons to Joomla's login forms. It was added as part of the Login with WebAuthn contribution back in 2020 (I contributed that code; you're welcome). I cannot tell you why your template does not support this core Joomla feature. Ask the company which sold it to you.

Are you seriously trying to mansplain me the Joomla core feature I wrote and contributed myself?! My dude, your anger is seriously misdirected.

I will just copy and paste the documentation for the Extra Login Buttons core Joomla! feature which I wrote myself — as I already told you — back on March 5th, 2020:

Extra login buttons

The plugin module and com_users now use the onUserLoginButtons event, defined and called in Joomla\CMS\Helper\AuthenticationHelper::getLoginButtons, to retrieve the definitions of any additional buttons which need to be placed after the regular login button.

All developers implementing a login module or, more generally, a login form should also use the Joomla\CMS\Helper\AuthenticationHelper::getLoginButtons public static method to retrieve said definitions and render these buttons to make their software fully compatible with Joomla 4.

Developers wishing to implement custom buttons should look at how the WebAuthn system plugin implements this functionality. Such buttons can be used for implementing third party single-sign-on services or even logging in using third party identity services such as those offered by popular social media (Facebook, Google, Twitter, GitHub etc).

This change does not adversely impact backwards compatibility. Third party login modules and login forms will continue functioning normally even if they do not implement the extra login buttons feature with the notable omission of integrations afforded by said feature such as Web Authentication itself. That is to say they won't stop functioning (which would be a b/c break) but they won't be feature-complete. Therefore the impact is much more benign that, for example, that of not including the Two Factor Authentication's Secret Code field back in Joomla! 3.2.

Providing a rendered button (HTML) is wrong. It means that extra buttons can only look one specific way, regardless of your template. This was the problem I had in Joomla 3 where Joomla did NOT have a way to render extra login buttons. As a result, the buttons looked alien with every template that wasn't Protostar.

Providing the data for the buttons (a PHP array) means that the view template of Joomla's mod_login and Joomla's com_users (or their template overrides which are part of your template and objectively the sole responsibility of the template developer) is responsible for rendering the buttons in a way that is suitable for display in whichever template you are using. Therefore, any template can render these extra buttons so that they do not look alien.

This is why I chose the latter method for my core contribution. I did it the right way and all reviewers agreed. The plugins are responsible for providing the data (PHP array) for the buttons, not the rendered button (HTML). That's what the SocialLogin plugins do.

Your template is NOT compatible with Joomla 4. Forget SocialLogin. Just enable the core Joomla! plugin “System - WebAuthn Passwordless Login”. Your template does not render the Log in with WebAuthn button in the login forms, proving that it's incompatible with Joomla 4 and it's 100% their responsibility for this mess.

I get it, you're unhappy that the plugin “doesn't work”. However, your ACTUAL problem is that your template doesn't work. Stop shouting at me. I am a victim here. My free of charge plugin works perfectly fine. The template you paid for does not work. If you want to give someone a proper blocking that should be the template developer who couldn't be arsed to find the 10' to update their template overrides for mod_login and com_users in the past 3 years. Yes, it only takes 10' to update the template overrides; I have done that myself on the template we are using on this very site here. Unlike template developers, I am not talking out of my ass; I've walked the walk before talking the talk, thank you very much.