Bug #44665
closed
Configuration Utility loses extension key
100%
Description
The EM's ConfigurationUtility::getCurrentConfiguration() method looks for the extension key at the wrong place. Rather than using the key it receives as a parameter, it tries to get it from $GLOBALS['TYPO3_LOADED_EXT'] where it does not exist (indeed it would be redundant information). As a result trying to read the current configuration always returns an empty array.
Notes:
- this is a first, trivial patch. Another one will be coming later, this is not the only error in this method.
- this bug is only visible when you update an extension's configuration, not when you simple display it.
Updated by Gerrit Code Review almost 12 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/17600
Updated by Gerrit Code Review almost 12 years ago
Patch set 1 for branch TYPO3_6-0 has been pushed to the review server.
It is available at https://review.typo3.org/17601
Updated by Francois Suter almost 12 years ago
Just a few more details about when this bug happens: it happens upon updating an extension's configuration when there are configuration sub-categories. The EM displays one submit button per subcategory and sends only that subcategory's data in the AJAX request to save the configuration. Since the current configuration is not read properly upon saving, values in the other subcategories are lost (= set back to default). This bug is invisible when there are no subcategories, because all current values are passed in the AJAX call.
Updated by Francois Suter almost 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset d99c4ebde93b5b036b4327e37d5b89e6f36ff066.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed