Problem/Motivation

Ability to use core OEmbed source but with an extra provider for cloudinary.

Proposed resolution/Remaining tasks

1. Provide a new provider for built-in Remote video OEmbed source

Comments

nginex created an issue. See original summary.

nginex’s picture

nginex commented
Status: Active » Closed (duplicate)

This was done in #3314722: Create a Cloudinary media source instead of a separate media type and will be tested there. Migration path will be provided in a new documentation for 3.x

nginex’s picture

nginex commented
Title: Switch from Video Embed Field to core OEmbed approach. » Cloudinary as dedicated provider for core OEmbed media.
Issue summary: View changes
Status: Closed (duplicate) » Active
Issue tags: +LutskGCW23

Need to check if it's still possible to add a new provider for OEmbed source. This might be usefull, so we can let users choose what to use: new media source Cloudinary or existing OEmbed source.

New code changes must be based on #3314722: Create a Cloudinary media source instead of a separate media type