TYPO3 Core

This behavior was introduced in changeset 2643, which adds user function support in the Constants Editor.

As part of a cleanup to the updatesForm() method, the processing was moved out of updatesForm() and into another method. The updatesForm() method is called from several locations, however, so this caused the missing extension configuration.

I've reverted updatesForm back to its original code and moved the check for whether the extension is installed into tsStyleConfigForm(), which is the actual method that renders the config form and extra fields.

committed to SVN on behalf of Jeff

It's still missing that the user is "forced" to update the configuration.

Now i debugged it, which wasn't an easy task, and i think i found a solution.

So normally when you install the extension, do the database updates, you are redirected to the last view (extension list, import, ...)

Now i check before redirection if there is an configuration, and if yes i redirect to the single view of the extension containing the configuration form.

Please have a look to the patch and test it