- Issue created by @jacobbell84
- Status changed to Needs review
12 months ago 7:27pm 8 August 2024 - First commit to issue fork.
- 🇩🇪Germany jurgenhaas Gottmadingen
I have created an MR and rebased that for the latest dev release.
Back in issue ✨ Add other field types Closed: works as designed there was a lot of work done getting a plugin system going. The component field functionality didn't make the cut for that release, so I thought I'd open a new issue to track it since I still need that functionality and it seems generally useful for a variety of plugins.
The attached patch follows the same approach as it did back in the old patch, but I updated it to work better with form improvements that have been made since that version of the module.
One known issue is that when you switch from the Default mapper plugin to a field specific one that supports component fields, you need to resave the configuration screen before those component fields will show. I imagine adding some sort of ajax callback on mapper switch could fix that issue.
Active
4.0
Code
I have created an MR and rebased that for the latest dev release.