I'm running Drupal 8.6.1 locally in Acquia Dev Desktop and I'm trying to add Remote Video (oEmbed) assets.

I have left the "Thumbnails location" at the default setting of public://oembed_thumbnails

When I attempt to add my first Remote Video media asset ( https://www.youtube.com/watch?v=anAQ794lsBM ) I get this error message that the thumbnail URI is not valid:

The website encountered an unexpected error. Please try again later.</br></br><em class="placeholder">InvalidArgumentException</em>: The URI &#039;public://oembed_thumbnails/6OpXFifNwFUlN09VaoQ-jzI3F_Tac971gZsWRAjnEqM.jpg&#039; is invalid. You must use a valid URI scheme. Use base: for a path, e.g., to a Drupal file that needs the base path. Do not use this for internal paths controlled by Drupal. in <em class="placeholder">Drupal\Core\Utility\UnroutedUrlAssembler-&gt;assemble()</em> (line <em class="placeholder">65</em> of <em class="placeholder">core\lib\Drupal\Core\Utility\UnroutedUrlAssembler.php</em>). <pre class="backtrace">Drupal\Core\Url-&gt;toString() (Line: 180)
Drupal\link\Plugin\Field\FieldFormatter\LinkFormatter-&gt;viewElements(Object, &#039;en&#039;) (Line: 80)
Drupal\Core\Field\FormatterBase-&gt;view(Object, &#039;en&#039;) (Line: 262)
Drupal\Core\Entity\Entity\EntityViewDisplay-&gt;buildMultiple(Array) (Line: 321)
Drupal\Core\Entity\EntityViewBuilder-&gt;buildComponents(Array, Array, Array, &#039;media_library&#039;) (Line: 263)
Drupal\Core\Entity\EntityViewBuilder-&gt;buildMultiple(Array) (Line: 220)
Drupal\Core\Entity\EntityViewBuilder-&gt;build(Array)
call_user_func(Array, Array) (Line: 378)
Drupal\Core\Render\Renderer-&gt;doRender(Array, ) (Line: 195)
Drupal\Core\Render\Renderer-&gt;render(Array) (Line: 1153)
Drupal\views\Plugin\views\field\FieldPluginBase-&gt;advancedRender(Object) (Line: 235)
template_preprocess_views_view_field(Array, &#039;views_view_field&#039;, Array) (Line: 287)
Drupal\Core\Theme\ThemeManager-&gt;render(&#039;views_view_field&#039;, Array) (Line: 437)
Drupal\Core\Render\Renderer-&gt;doRender(Array, ) (Line: 195)
Drupal\Core\Render\Renderer-&gt;render(Array) (Line: 1743)
Drupal\views\Plugin\views\field\FieldPluginBase-&gt;theme(Object) (Line: 761)
Drupal\views\Plugin\views\style\StylePluginBase-&gt;elementPreRenderRow(Array)
call_user_func(Array, Array) (Line: 378)
Drupal\Core\Render\Renderer-&gt;doRender(Array, ) (Line: 195)
Drupal\Core\Render\Renderer-&gt;render(Array) (Line: 709)
Drupal\views\Plugin\views\style\StylePluginBase-&gt;renderFields(Array) (Line: 576)
Drupal\views\Plugin\views\style\StylePluginBase-&gt;renderGrouping(Array, Array, 1) (Line: 468)
Drupal\views\Plugin\views\style\StylePluginBase-&gt;render(Array) (Line: 2111)
Drupal\views\Plugin\views\display\DisplayPluginBase-&gt;render() (Line: 131)
Drupal\webprofiler\Views\TraceableViewExecutable-&gt;render() (Line: 183)
Drupal\views\Plugin\views\display\Page-&gt;execute() (Line: 1630)
Drupal\views\ViewExecutable-&gt;executeDisplay(&#039;page&#039;, Array) (Line: 77)
Drupal\views\Element\View::preRenderViewElement(Array)
call_user_func(Array, Array) (Line: 378)
Drupal\Core\Render\Renderer-&gt;doRender(Array, ) (Line: 195)
Drupal\Core\Render\Renderer-&gt;render(Array, ) (Line: 226)
Drupal\Core\Render\MainContent\HtmlRenderer-&gt;Drupal\Core\Render\MainContent\{closure}() (Line: 582)
Drupal\Core\Render\Renderer-&gt;executeInRenderContext(Object, Object) (Line: 227)
Drupal\Core\Render\MainContent\HtmlRenderer-&gt;prepare(Array, Object, Object) (Line: 117)
Drupal\Core\Render\MainContent\HtmlRenderer-&gt;renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber-&gt;onViewRenderArray(Object, &#039;kernel.view&#039;, Object) (Line: 76)
Drupal\webprofiler\EventDispatcher\TraceableEventDispatcher-&gt;dispatch(&#039;kernel.view&#039;, Object) (Line: 156)
Symfony\Component\HttpKernel\HttpKernel-&gt;handleRaw(Object, 1) (Line: 68)
Symfony\Component\HttpKernel\HttpKernel-&gt;handle(Object, 1, 1) (Line: 57)
Drupal\Core\StackMiddleware\Session-&gt;handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\KernelPreHandle-&gt;handle(Object, 1, 1) (Line: 99)
Drupal\page_cache\StackMiddleware\PageCache-&gt;pass(Object, 1, 1) (Line: 78)
Drupal\page_cache\StackMiddleware\PageCache-&gt;handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware-&gt;handle(Object, 1, 1) (Line: 38)
Drupal\webprofiler\StackMiddleware\WebprofilerMiddleware-&gt;handle(Object, 1, 1) (Line: 52)
Drupal\Core\StackMiddleware\NegotiationMiddleware-&gt;handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel-&gt;handle(Object, 1, 1) (Line: 665)
Drupal\Core\DrupalKernel-&gt;handle(Object) (Line: 19)
</pre>

However the folder C:\Users\Nick\Sites\devdesktop\drupal\sites\drupal.dd\files\oembed_thumbnails does get created and an appropriate thumbnail named 6OpXFifNwFUlN09VaoQ-jzI3F_Tac971gZsWRAjnEqM.jpg is placed within it.

I am not sure whether this is a bug or I am using an inappropriate thumbnails location. I tried a few different options but no success. What thumbnails location should I be using in a local Dev Desktop environment?

Comments

Nick Hope created an issue. See original summary.

nick hope’s picture

I discovered that this issue only happens when I map the Local URI of the thumbnail to a field in the FIELD MAPPING section of Media Type edit page. If I leave it as "- Skip field -" then I don't get the problem.

I have tried making the field type (of the field that I map it to) both a Link and a Text (plain), but same problem with either.

I have tried with both YouTube and Vimeo remote video and get the same problem.

So I suppose the issue could be defined as "In a remote video media type, cannot map the 'local URI of the thumbnail' to a field".

phenaproxima’s picture

Issue tags: +oembed

Version: 8.6.1 » 8.6.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.6.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

acbramley’s picture

Status: Active » Closed (outdated)
Issue tags: +Bug Smash Initiative

This seems like a potentially outdated or 1 off issue given the age and lack of comments.

I'm going to go with my gut and close as outdated but please feel free to reopen the issue if needed with steps to reproduce from a fresh drupal install