Processor for OEmbed sources

Created on 9 February 2023, over 1 year ago
Updated 18 December 2023, 6 months ago

Provides a Processor to support Media entities with an OEmbed source.

✨ Feature request
Status

Postponed: needs info

Version

3.0

Component

Code

Created by

🇬🇧United Kingdom Leo Pitt

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Leo Pitt
  • 🇬🇧United Kingdom 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 about 1 year ago
  • 🇦🇹Austria fago Vienna
  • 🇸🇮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
  • 🇸🇮Slovenia useernamee Ljubljana
  • Issue was unassigned.
  • Status changed to Postponed: needs info 7 months ago
  • 🇦🇹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

Production build 0.69.0 2024