Make SUPPORTED_CUSTOM_FIELD_PLUGINS configurable for better plugin compatibility

[yunusyuksel]

In my application, I’m using the strapi-plugin-tagsinput
plugin, and I’d like the fields created by this plugin to be translatable as well.

Currently, the SUPPORTED_CUSTOM_FIELD_PLUGINS list is static. Would it be possible to include this plugin in that list, or alternatively make it configurable so that users have more control over which custom fields can be exported or translated?

Thanks!

[david-vaclavek]

Hello, @yunusyuksel.

Thanks for the suggestion — this is more of a feature request than an issue.
You’re actually the first one to ask for support for the strapi-plugin-tagsinput plugin, so thanks for bringing it up!

At the moment, our focus is elsewhere, and realistically we wouldn’t be able to consider this before Q2 2026.
That said, since this is an open-source project, we’d love to see contributions from the community.

If you’d like to give it a try:
• You can spin up an instance, link the plugin, and extend the supported custom field plugins list.
• Once you’ve got a tested working solution, feel free to open a PR — I’ll be happy to review it personally.

If you need any guidance or mentoring while working on it, don’t hesitate to reach out at david@localazy.com — we can even jump on a quick call to go through the implementation together.

And as a thank-you, we’ll be happy to send you a small reward for your contribution.

Thanks again for your input and for helping us make the plugin better!