[TYPO3-core] RFC #14727: Code cleanup: tx_saltedpasswords_sv1 should use parent object instead of TYPO3_MODE

Steffen Gebert steffen at steffen-gebert.de
Sat Jan 8 14:27:28 CET 2011


> Bugtracker references:
> http://bugs.typo3.org/view.php?id=0014727
>
> Branches:
> trunk
>
> Problem:
> At the moment, tx_saltedpasswords_sv1 uses the TYPO3_MODE constant to
> determine in which table the password should be updated (in
> updatePassword() method).
> This isn't very clean and can lead to problems if you use some kind of
> be/fe login combination extension like simulatebe. There, the user
> logs in to the Frontend, to TYPO3_MODE is "FE" but wants to
> authenticate a BE user.
>
> Solution:
> A simple solution to this is the usage of the $pObj field. See the
> attached patch. It makes things much simpler and cleaner as far as I
> can see.

+1 by reading and testing

Attached a cleaned-up patch against svn root.

Kind regards
Steffen

-- 
Steffen Gebert
TYPO3 Core Team Member

Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 14727_v2.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20110108/cd714e12/attachment.txt>


More information about the TYPO3-team-core mailing list