Bug #66412
closed
Saving own user configuration fails when exclude fields are configured
Added by Benjamin Serfhos over 9 years ago.
Updated about 6 years ago.
Description
The \TYPO3\CMS\Setup\Controller\SetupModuleController::storeIncomingData() forces the update for the user even if he is not admin. If the fields are however by external functionality excluded, this does not work anymore.
Howto reproduce;
// Force all fields to exclude for users
foreach ($GLOBALS['TCA']['be_users']['columns'] as $key => &$configuration) {
if (!isset($configuration['exclude'])) {
$configuration['exclude'] = 1;
}
}
Now as editor their data in the user tools cannot be edited by them.
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38684
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38684
I'm failing to understand the usecase.
A normal user never has access to the be_user record. So why having exclude fields?
The usecase is for user maintenance by a module for "super users".
I have a module for backend users so they can adjust other "regular users" via default TCA configuration.
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38684
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38684
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/39049
- Status changed from Under Review to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF