Problem/Motivation

I have this error when trying to use drush command when orejime is installed:
You have requested a non-existent service "media.oembed.resource_fetcher".

Proposed resolution

I realized that the Media module providing the service "media.oembed.resource_fetcher" was not active on that website. After activating Media module, I was then able to run drush commands without error.

Maybe Orejime should add a dependencie to Media to avoid this situation even if media is probably enabled on many sites.
EDIT: Or maybe orejime shoul not call this service if the media module is not enabled?

CommentFileSizeAuthor
#7 3546724-7.patch601 bytesjohnatas

Issue fork orejime-3546724

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:

About issue forks

Comments

davidiio created an issue. See original summary.

davidiio’s picture

davidiio commented
Issue summary: View changes

johnatas made their first commit to this issue’s fork.

johnatas opened merge request !16

johnatas’s picture

johnatas commented

Hello,

I’ve just opened a MR that adds the missing dependencies:

  • drupal:media used in OEmbedOrejimeFormatter + OrejimeResourceFetcher
  • drupal:views used in OrejimeViewsData
johnatas’s picture

johnatas commented
Status: Active » Needs review
johnatas’s picture

johnatas commented
StatusFileSize
new 3546724-7.patch601 bytes

Hello,

Attached is a patch for version 3.0.0-alpha2 of the module.

fabsgugu’s picture

fabsgugu commented

Hello,

I don't think it is necessary to put in required "drupal:content_translation".

johnatas’s picture

johnatas commented

Hey,

You're right, that was my mistake — it's fixed now. 😉

fabsgugu’s picture

fabsgugu commented
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.

Status: Fixed » Closed (fixed)

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