You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful for my needs if I could prepare the general TCA configuration for imports through a custom extension but set it to invisible/disabled, and then activate it via TCA in the site package when needed.
Currently, I always have to set the entire general TCA configuration for each site package
The text was updated successfully, but these errors were encountered:
I don't really understand your need. How would that activation work?
What about wrapping the configuration in some method and calling it, like \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig for media field did up to TYPO3 11?
in my case I have my own extension which I fill by import but there are different sources for the data so I want to prepare the import configuration in the extension (as 2 import configurations for source a and b) and for each project in the site package only do something like $GLOBALS['TCA']['myDbModel']['external']['general']['myConfigurationForA']['enable'] = true so that the unnecessary configuration for source B does not appear in the BE in the import module
but thanks for the tip about wrapping the configuration in some method and calling it, like \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfiglike\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig that could
Thanks for the details. I had a similar setup recently, so it could be an interesting feature to add in the future. I hadn't thought about a simple "disable" flag as you suggest, which would be easy to implement.
It would be helpful for my needs if I could prepare the general TCA configuration for imports through a custom extension but set it to invisible/disabled, and then activate it via TCA in the site package when needed.
Currently, I always have to set the entire general TCA configuration for each site package
The text was updated successfully, but these errors were encountered: