Problem/Motivation

In issue #3541992, I hadn’t noticed that the schema for the OEmbed formatter was also missing.

[warning] Schema errors for core.entity_view_display.media.remote_video.default with the following errors: core.entity_view_display.media.remote_video.default:content.field_media_oembed_video.settings.image missing schema, core.entity_view_display.media.remote_video.default:content.field_media_oembed_video.settings.image_style missing schema, core.entity_view_display.media.remote_video.default:content.field_media_oembed_video.settings.aria_label missing schema. These errors mean there is configuration that does not comply with its schema. This is not a fatal error, but it is recommended to fix these issues. For more information on configuration schemas, check out <a href="https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-schemametadata">the documentation</a>.

Steps to reproduce

  1. Enable the module.
  2. Choose a field that can be embedded (for example, the field_media_oembed_video field of the native Remote Video media type).
  3. In the display settings, set its format to “OEmbed Orejime: Iframe Consent”.
  4. Save.

The warning may also appear in the Configuration Inspector.

Proposed resolution

  • Add the formatter mapping to the configuration schema.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork orejime-3551393

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

johnatas created an issue. See original summary.

johnatas’s picture

Status: Active » Needs review
fabsgugu’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

johnatas’s picture

Thanks fabsgugu,

please don’t forget the credits ♥

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.