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

Ability to select the field for integration via a custom field name #2

Open
lukewhitmore opened this issue Aug 31, 2021 · 3 comments
Open

Comments

@lukewhitmore
Copy link

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.

@Berdir
Copy link
Member

Berdir commented Aug 31, 2021

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.

@lukewhitmore
Copy link
Author

[..] 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.

@Berdir
Copy link
Member

Berdir commented Aug 31, 2021

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.

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