Issue Bug Closed

#44665Configuration Utility loses extension key

Francois Suter 01/19/13, 21:48 updated 10/23/17, 22:16

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:

  1. this is a first, trivial patch. Another one will be coming later, this is not the only error in this method.
  2. this bug is only visible when you update an extension’s configuration, not when you simple display it.

Reviews 2