[BUGFIX] Move beuser property mappings to global scope 67/23967/4
authorPhilipp Gampe <philipp.gampe@typo3.org>
Mon, 23 Sep 2013 10:00:55 +0000 (12:00 +0200)
committerStefan Neufeind <typo3.neufeind@speedpartner.de>
Mon, 23 Sep 2013 21:54:19 +0000 (23:54 +0200)
commit68e91ccaa14166d7a881a42b4a987924c1462963
tree7992b70fde3356960a9448ac27c25283340074d8
parentd46858dfbd110ab216ae8de41c90f55cf7bc86c7
[BUGFIX] Move beuser property mappings to global scope

Currently the persistence settings for all tx_beuser models are defined
in module.tx_beuser.persistence.classes.
If any other module tries to access the corresponding backend user
repository from tx_beuser, then no mappings will be loaded by extbase,
resulting in a wrong cache entry for the model and the attempt to
access a nonexisting table.

Move the class mapping part of the TS template into
  config.tx_extbase.persistence.classes
to make them available for all extensions and modules.

Resolves: #51234
Releases: 6.2, 6.1, 6.0
Change-Id: I0b39c96c9db89c379e5613231a215f27b2dfbcde
Reviewed-on: https://review.typo3.org/23967
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
typo3/sysext/beuser/Configuration/TypoScript/setup.txt