Bug #41281
closed
TypoScript template does not support "type=input" any more
100%
Description
In order to allow admins to configure an extension via the Extension Manager, file ext_conf_template.txt can be used. This TypoScript template file may include keywords such as:
# cat=basic/enable; type=string; label=Enter description here...
As documented (currently for TYPO3 4.7):
http://typo3.org/documentation/document-library/core-documentation/doc_core_ts/4.7.0/view/1/3/#id449667
Some extensions use "type=string" (which is correct), others use "type=input" (which worked fine up to TYPO3 version 4.7.x). Extensions such as "tt_news" (version 3.3.0) or "nagios" (version 1.2.4) use "type=input".
In TYPO3 version 6.0.0 beta2, the Extension Manager does not show an input field but open/close brackets () instead, see attached screenshot. So, extensions which have "type=input" can not be configured properly.
Due to the fact that "type=input" is officially not defined, this is a bug in the extensions, not in TYPO3 nor the extension manager. However, I suspect it would become a bigger problem if a lot of extensions can not be configured any more (e.g. after an update to TYPO3 v6); even if the extensions use the v6 API (the deprecation log does not show any hints).
Please note: "type=input" worked in the past (I assume it falls back to the default type "string") and I wonder if removing this mechanism was intended.
Files
Updated by Michael Schams about 12 years ago
- File screenshot0004.png screenshot0004.png added
Updated by Xavier Perseguers about 12 years ago
As "input" was never a recognized type, I wonder why people used this type in the first place. I don't consider this a bug in Core itself and I'd even say that if someone wants to "fix" it, it should be officially supported then, and the documentation should be adapted to reflect this change as well.
Updated by Jigal van Hemert about 12 years ago
Looking at the old code I found that the type 'string' isn't even explicitly mentioned. 'small' (this type is missing in the documentation!) and everything that doesn't match any of the other types is handled as an input field.
In the new EM the types are handled by a mapping. For the sake of backwards compatibility I think we should add the type 'input' in the the new EM without adding it to the documentation. I don't think people have made it up themselves; it may have been copied from really old extensions.
Updated by Gerrit Code Review about 12 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15379
Updated by Michael Schams about 12 years ago
I understand that the patch has been already pushed to the review server, so the issue is (almost) solved.
However, I wrote a script that reads the latest version of all extensions (t3x files) and extracts an "ext_conf_template.txt" file if it exists. The script then checks for the appearance of "type=input" in these files. The outcome of this test as follows:
5731 extensions examined.
35 of them have a "type=input" declaration in the ext_conf_template.txt file.
See attached file "forge-41281-list-of-affected-extensions.txt".
Updated by Christian Kuhn about 12 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Resolved: patch was merged.
Updated by Oliver Hader over 11 years ago
- Project changed from 2269 to TYPO3 Core
Updated by 