Topic-icon New Login/Logout Joomla 4.3.2 setting

Active Subscriptions:

None
11 months 4 weeks ago #68561 by joomleb
Hi guys,
this new setting should be considered and added also here in JFBC  github.com/joomla/joomla-cms/pull/40539

Do you agree?
The topic has been locked.
Support Specialist
7 months 2 weeks ago #68632 by mel
If you use SCLogin to log in with Joomla credentials, the behavior for log in messages will be controlled by Joomla Users component. We just pass along credentials to com_users to do the log in. We automatically would pick up this change.

If using social login to log in with social credentials, the amount of messages enqueued and displayed in the front-end is controlled by the JFBConnect > Configuration > Advanced > Debugging Mode option. If set to Logging only or Off, most messages would not be added to the front-end.

-Melissa
The topic has been locked.
Active Subscriptions:

None
7 months 2 weeks ago #68634 by joomleb
Hi guys,
@Mel with Joomla 4.3 the workflow has changed:
#40539 [4.3] Remove message on login
github.com/joomla/joomla-cms/pull/40539

Maybe, that can be the reason
And maybe would be good to "apply" the same behaviour on SCLogin
The topic has been locked.
Support Specialist
7 months 2 weeks ago #68635 by mel
What I'm saying is the same behavior is applied automatically when using Joomla credentials. Are you referring only to social login?
The topic has been locked.
Active Subscriptions:

None
7 months 2 weeks ago #68640 by joomleb
Hi Mel,
due that I wrote it long time ago I'm really not sure if I remember well what I found during my testings :D :)

Anyway, what I mean here is to pay attention that Joomla changed the workflow (messages has been deprecated), read carefully the GitHub ticket and it's related tickets.
The same should happen during Login/Logout through SCLogin and JFBConnect Social Login (maybe they are calling Login/Logout SC language strings)
The topic has been locked.
Support Specialist
7 months 2 weeks ago #68661 by mel
SCLogin has no enqueueMessage calls. JFBConnect only does a forced enqueue message when there is an error that prevents JFBConnect from running. By default, the rest of the informational/workflow messages (which it seems that the github ticket is referring to) are disabled unless the admin turns on debug in the JFBC advanced area. I think we match what they're going for, with no additional change.
The following user(s) said Thank You: joomleb
The topic has been locked.