The current and last release of Joomla 2.5 is .28

Before proceeding any further please update to this version and re-test.
obviously there have been a lot of bug and security fixes since .19 was
released

On 17 December 2014 at 11:20, rriemvis notifications@github.com wrote:

Steps to reproduce the issue

Setup a site with guest and registered type of users with a standard login
access on a menu item. Non-registered users should be given guest
permissions.
Define a menu item that can only be accessed with registered user rights.
Try to access this menu item by providing the URL directly without being
logged in.
Now the login form should appear.

Try to log in with an existing user but wrong password.
You should get an error message.
Now try to log in with the correct password.
Expected result

You are redirected to the target menu link.
Actual result

You are not redirected to the target menu link.
System information (as much as possible)

Joomla 2.5.19, basic setup with guest and registered users
Additional comments

The reason for this is that the return URL which is passed in the form as
a hidden input parameter is not preserved after reloading the login page
due to the login error.

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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Dear Brian,

The problem is exactly the same after the update to 2.5.28. Is rather logical as there has been no change in the com_users/controllers/user.php file between the 2 versions.

Thanks,

Ruud

From: Brian Teeman [mailto:notifications@github.com]
Sent: mercredi 17 décembre 2014 12:33
To: joomla/joomla-cms
Cc: rriemvis
Subject: Re: [joomla-cms] return URL is not preserved after login failure page reload (#5454)

The current and last release of Joomla 2.5 is .28

Before proceeding any further please update to this version and re-test.
obviously there have been a lot of bug and security fixes since .19 was
released

On 17 December 2014 at 11:20, rriemvis < notifications@github.com notifications@github.com> wrote:

Steps to reproduce the issue

Setup a site with guest and registered type of users with a standard login
access on a menu item. Non-registered users should be given guest
permissions.
Define a menu item that can only be accessed with registered user rights.
Try to access this menu item by providing the URL directly without being
logged in.
Now the login form should appear.

Try to log in with an existing user but wrong password.
You should get an error message.
Now try to log in with the correct password.
Expected result

You are redirected to the target menu link.
Actual result

You are not redirected to the target menu link.
System information (as much as possible)

Joomla 2.5.19, basic setup with guest and registered users
Additional comments

The reason for this is that the return URL which is passed in the form as
a hidden input parameter is not preserved after reloading the login page
due to the login error.

—
Reply to this email directly or view it on GitHub
< #5454 https://github.com/joomla/joomla-cms/issues/5454>.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

—
Reply to this email directly or view it on GitHub #5454 (comment) . https://github.com/notifications/beacon/AJvxiTCqvrH-cZ_xSRv_slxaV8tweiFvks5nYWFOgaJpZM4DJdX5.gif

Your conclusion about it being logical because one file is unchanged is wrong. The file you mention is a controller which relies on a lot of the other files. Also this controller is called in a certain context and acts based on that.

That is why the policy of raising issues is as mentioned by @brianteeman !

Got it and accept your remarks.

The error however still remains after the full core update.

Thanks,

Ruud

From: sovainfo [mailto:notifications@github.com]
Sent: samedi 20 décembre 2014 12:25
To: joomla/joomla-cms
Cc: rriemvis
Subject: Re: [joomla-cms] return URL is not preserved after login failure page reload (#5454)

Your conclusion about it being logical because one file is unchanged is wrong. The file you mention is a controller which relies on a lot of the other files. Also this controller is called in a certain context and acts based on that.

That is why the policy of raising issues is as mentioned by @brianteeman https://github.com/brianteeman !

—
Reply to this email directly or view it on GitHub #5454 (comment) . https://github.com/notifications/beacon/AJvxiVZNDW5eOz3PR5GbV65KFeLkitImks5nZVQkgaJpZM4DJdX5.gif

I'm closing this issue since Joomla 2.5 is no longer supported and thus this will not be fixed anymore.
If the issue still exists in Joomla 3.x, please open a new issue for it.