You are using a custom login handler. This will be automatically disabled when upgrading to v5.

[D-Rocks09]

Hello-

I have inherited a community that I am now the owner after the previous owner stepped down. I am not a complete novice; however, where can I find my custom login handler and what should I do to remedy it before v5?

[Hatsu]

In ACP -> System -> Settings -> Login&Registration maybe? I myself have no experience with this.

Edited December 1 by Hatsu

[Marc]

You can disable from the area mentioned above. If you wish to use it once on v5, it would need to be rewritten for that version by the developer of that custom login handler

[Shawn RR]

17 hours ago, Marc said:

You can disable from the area mentioned above. If you wish to use it once on v5, it would need to be rewritten for that version by the developer of that custom login handler

This might be a little bit off topic but when it comes to a login handler needing to be rewritten is the original code already available? What would be the steps to begin preparing for that kind of revision. 

[Marc]

Im not a developer myself, and I would suggest speaking to the developer of your login handler on that. 

[Gabriel Torres]

I have a silly question about this. Does "custom login handler" mean a login done with anything different from email+password combo? I ask this as we have Google/Microsoft/Facebook/Linkedin login handlers, but they are not "custom" IMO, as they are part of the core software and not added by an app/plugin. 

I guess my question is: in v5, we will only have email+password login option or we still have the option to set other login options (Google, Facebook etcetera)?

Thanks.

[Jim M]

"Custom" is anything which is not a part of the core software, aka you had to have specially developed or downloaded from a third party author. So the login handlers which are supported by us will be present, i.e. Standard, Google, Facebook, etc...

[Gabriel Torres]

Thanks @Jim M. I've found the culprit. We had installed a custom login method ages ago and have since deleted it, however the records where still present in the database (core_login_handlers. core_login_methods, core_login_links). I've manually deleted these orphan records and now the warning message (You are using a custom login handler. This will be automatically disabled when upgrading to v5) is gone. Thanks.