Topic-icon jfbconnectauthfailure

Active Subscriptions:

None
10 years 7 months ago #36823 by micfre
jfbconnectauthfailure was created by micfre
Hi,

we are looking for internal error message on our website and read the error lock file. what we see is many of errors
2013-09-16T23:57:39+00:00 INFO jfbconnectauthfailure Benutzername und Passwort falsch oder das Benutzerkonto existiert noch nicht!

Activ are only one FAcebook component and plugin. Only JFB.

What is our mistake.We can logged in fine and other user con do it too. I think get the internal error from this. It comes if we switched 10 times or until 15 times the pages into the frontend.

We used as template gantry 4.1.17
Joomsef 4 newest (disable at time)
Hwdmediashare (Facebook plugins disabled) only the like under pictures works. i think he grabb your connectplugin
RSforms!Pro
jnews
Joomla 3.1.5

Best
Michael
The topic has been locked.
Support Specialist
10 years 7 months ago #36831 by alzander
Replied by alzander on topic jfbconnectauthfailure
Michael,
The issue isn't with JFBConnect at all, the JFBConnect Authentication plugin is simply ordered 'last' (highest number) in the Plugin Manager. Because of that, all authentication failures look like they are coming from JFBConnect. So, even if a user simply enters a bad Joomla username/password, it will look like JFBConnect denied the user.

If you switch the authentication ordering so Joomla is last, the same amount of errors will show, but they'll all look to come from the Joomla login system.

It's a silly bug on Joomla's part, and not something we can fix.

I hope that makes sense,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 7 months ago #36932 by micfre
Replied by micfre on topic jfbconnectauthfailure
Hi Alex,

i understand ;-) So we will wait of any Joomla Version thex be fix it

Best
Michael
The topic has been locked.
Support Specialist
10 years 7 months ago #36938 by alzander
Replied by alzander on topic jfbconnectauthfailure
It's likely not going to be fixed anytime soon, and really is just a logging problem. Either way, glad we could explain.

Alex
The topic has been locked.