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

Alexander Stehlik alexander.stehlik at googlemail.com
Tue Jun 15 12:30:57 CEST 2010


Hi,
This is an SVN patch request.

Type: Code cleanup

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.

Kind regards,

Alex.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch_0014727.diff
Type: text/x-patch
Size: 1454 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100615/a41eb0f8/attachment.bin>


More information about the TYPO3-team-core mailing list