Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] "invisible/disabled"-Flag for Connector General TCA configuration #365

Open
bh-teufels opened this issue Jan 10, 2025 · 3 comments

Comments

@bh-teufels
Copy link

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

@fsuter
Copy link
Contributor

fsuter commented Jan 10, 2025

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?

@bh-teufels
Copy link
Author

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

@fsuter
Copy link
Contributor

fsuter commented Jan 13, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants