Bug #51829
closed
TCEmain::log relies on active BE_USER
0%
Description
Several developers abuse t3lib_TCEmain and instantiate it also in other
contexts than BE, for which it never was made.
As this breaks several extensions that use it in FE or CLI mode and the
fix is trivial, avoid crashing.
In case logging is enabled but there exists no BE_USER, simply prevent logging.
Updated by Gerrit Code Review about 11 years ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/23670
Updated by Gerrit Code Review about 11 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/23670
Updated by Jigal van Hemert about 11 years ago
In CLI context there can be a valid backend user. If a scheduler task is used the user cli_scheduler should exist and can be given rights to modify the necessary tables. If the cli dispatch script is used the cli code checks for a backend user with the lower case name of what was registered in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['GLOBAL']['cliKeys'][<extensionkey>] as second array element (name there must start with '_CLI' (upper case), BE user must be same in lower case).
So, if DAM registers a cli key it can for example provide the name for a BE user as _CLI_dam. If that user exists it will be used in CLI context.
Updated by Gerrit Code Review almost 10 years ago
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/23670
Updated by Gerrit Code Review almost 10 years ago
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/23670
Updated by Mathias Schreiber almost 9 years ago
- Status changed from Under Review to Rejected