Task #53852
closed[FE][defaultTypoScript_setup] -> textarea
100%
Description
Hi,
in the install tool, under "All Configuration" -> $TYPO3_CONF_VARS['FE'], there is an input field for default TypoScript setup. The corresponding field for TypoScript constants right above it is a textarea. I never understood the reason why one got a textarea while the other should only be an input field, since a setup usually can have quote some lines...
Please correct me if I am wrong, but if not, I would like to see the TypoScript setup field to be a textarea in 6.2.
Thank you!
Robert
Updated by Markus Klein almost 11 years ago
- Priority changed from Could have to Should have
- Target version changed from 6.2.0 to next-patchlevel
- TYPO3 Version changed from 6.2 to 4.5
- Complexity set to no-brainer
Hi Robert!
Wow, this dates back to commit 2bb0575007d5e22eba5ee02929da30d862f33428 from Nov 6th 2009.
Nice catch.
In 6.1 the defaultTypoScript_setup field does not even show up in the Install Tool.
Updated by Markus Klein almost 11 years ago
- Tracker changed from Feature to Task
- TYPO3 Version changed from 4.5 to 6.2
Hm... found #24129, where there were troubles with lots of code being displayed in the field and then this code was stored again to localconf.php
In my 6.2 blank installation the field now was empty, but I don't know how this behaves if (older) extensions come into the game.
Anyway I'll push the patch, but I'll limit it to 6.2 again.
Updated by Gerrit Code Review almost 11 years ago
- 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 https://review.typo3.org/25634
Updated by Christian Kuhn almost 11 years ago
Issue #24129 (this field showing lots of data) is not valid anymore: ExtensionManagementUtility has some methods (addTypoScriptSetup) that add content to this string and those should be called in ext_localconf.php. So, in the old days, when some ext used this API, this field was filled with this content.
Nowadays, all configuration does not evaluate ext_localconf and ext_tables of arbitrary extensions anymore (only extbase, fluid and maybe dbal), so this can now be changed, imho.
Updated by Markus Klein almost 11 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset c7f4df4e4cb07248a6d91161c5be249c5867b3fb.