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
There's an alteration that we'd like to make re. the field that's used for the integration.
Currently, the media entity that's used for integration requires the presence of a specifically named image field.
Would be really useful to be able to select the field name that's used for integration, so existing media entity bundles can be integrated without too much refactoring.
The text was updated successfully, but these errors were encountered:
Patches/pull requests welcome to make this more configurable, keep in mind that you still need separate media bundles with a bynder source plugin, I assume you meant just reusing existing fields that are in use on other bundles.
[..] keep in mind that you still need separate media bundles with a bynder source plugin, I assume you meant just reusing existing fields that are in use on other bundles.
That's a really good point, thanks. We'd need to be able to update the source plugin to augment current media bundles to work with Bynder.
This will not help then or won't be enough at least. The bynder source is still very much required and expect to be there, this just adds a local copy for the bynder media asset. For SNS Updates and so on to work, that is required.
If you want it to work with your existing bundles, your only option is writing your own version of the entity browser plugin that downloads and copies the asset into your existing media types.
There's an alteration that we'd like to make re. the field that's used for the integration.
Currently, the media entity that's used for integration requires the presence of a specifically named image field.
Would be really useful to be able to select the field name that's used for integration, so existing media entity bundles can be integrated without too much refactoring.
The text was updated successfully, but these errors were encountered: