- Issue created by @Leo Pitt
- 🇦🇹Austria fago Vienna
That seems fine to me. As it's changing default output, we should move it to 3.x again. Could you share an example output as well?
- Status changed to Needs review
over 1 year ago 3:39pm 27 April 2023 - 🇸🇮Slovenia useernamee Ljubljana
I think that code changes look good, I'm just not sure how much advantage this custom OEmbed processor brings over the default
MediaReferenceFieldItemProcessor. Does it not render the media entity? - Assigned to fago
- Issue was unassigned.
- Status changed to Postponed: needs info
about 1 year ago 3:53pm 20 November 2023 - 🇦🇹Austria fago Vienna
I've not been suggesting this change, Leo Pitt could you clarify?
But given we are not working on getting a configurable CE-UI in, I think this should be simply one of the options available, then there is no need for a special-case processor in 3.x.So it would make sense to move this into a custom module for now, and make sure 3.x custom elements UI can be configured to use field formatters. Leo Pitt, would that work for you?
- 🇬🇧United Kingdom Leo Pitt
Hi,
Sorry for the lack of reply. I contributed this issue while deeply involved in a project using Custom Elements, but I have since started on different work and so it hasn't been on my radar for a while.
I'm afraid I cannot remember why it was necessary to create an OEmbed Processor, as it's been a few months since I worked on this.
fago, I'm fine with your proposed option. If anyone else has a requirement for this, then they will be able to find and resurrect the issue.
Thanks