? Success

User tests: Successful: Unsuccessful:

avatar pasamio
pasamio
6 Jan 2014

The onUserLoginFailure trigger is a user plugin method however on the failure code path, it isn't loaded. So this changes that to put it on the main code path ahead of the failure check.

avatar pasamio pasamio - open - 6 Jan 2014
avatar betweenbrain
betweenbrain - comment - 17 Jan 2014

Thanks Sam!

This seems like a logical fix. Is there a tracker item for this and/or
testing instructions?

Best,

Matt Thomas
@betweenbrain
http://matt-thomas.me/
http://betweenbrain.com/
https://github.com/betweenbrain

Sent from mobile. Please pardon any typos or brevity.
On Jan 6, 2014 12:37 PM, "Sam Moffatt" notifications@github.com wrote:

The onUserLoginFailure trigger is a user plugin method however on the
failure code path, it isn't loaded. So this changes that to put it on the

main code path ahead of the failure check.

You can merge this Pull Request by running

git pull https://github.com/pasamio/joomla-cms patch-1

Or view, comment on, or merge it at:

#2761
Commit Summary

  • Import the user plugins for onUserLoginFailure

File Changes

Patch Links:


Reply to this email directly or view it on GitHub#2761
.

avatar roland-d
roland-d - comment - 12 Jul 2014

@test: works as expected. After applying the patch the onUserLoginFailure() is triggered in the frontend.

Is this supposed to be triggered in the backend as well?

There is a CS issue in the PR:

:10: trailing whitespace.
JPluginHelper::importPlugin('user');
warning: 1 line adds whitespace errors.

avatar pasamio
pasamio - comment - 12 Jul 2014

Fixed the whitespace error.

avatar Bakual Bakual - change - 14 Jul 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-07-14 19:25:04
avatar Bakual Bakual - close - 14 Jul 2014

Add a Comment

Login with GitHub to post a comment