🇺🇸United States @amaria

@jan we had to do the same

Thanks @webflo. No worries. It's fixed in 8.x-1.9 and 10 in the other issue.

Thanks @deepakkm. Just to confirm, it appears to be fixed in 8.x-1.x (dev) but not 8.x-1.8.

Please remove webmozart/path-util from the composer.json file if it is no longer in use. It is causing a message about "abandoned package" during "composer audit". See https://www.drupal.org/project/composer_deploy/issues/3473097 📌 webmozart/path-util is abandoned Active

This is not fixed by https://www.drupal.org/project/composer_deploy/issues/3429433 📌 Automated Drupal 11 compatibility fixes for composer_deploy Needs review as that is still requiring "webmozart/path-util": "^2.1.0" in the composer.json file.

I'm getting the same thing.

1. Created an entity browser with Upload and Embed code widgets.
2. Created a Media Entity Reference field for Image and Remote Video
3. Edit the content type containing the above field
4. Try entering URL or Embed code for YouTube and I get the subject error.

Try creating a Remote Video from Media admin, it works.

vasike → credited amaria → .

I am still having a problem with this. After updating my field schema with a new column, and use code from #60/#66 in an update hook, it doesn't work.

When I get the columns from the table mapping...
$columns = $table_mapping->getColumnNames($field_name);
It does not contain the new property yet so it fails at this...
$field_exists = $schema->fieldExists($table_name, $columns[$property]);

Am I missing something before I run this code?

The patch in #36 fixes this issue.

@liquidcms, any luck with your patches? I'd like to try them as I'm having similar issues with content moderation + multilingual + paragraphs (or ERR) + IEF.

• Create and publish EN and SP version of content that has a Paragraph field using IEF widget, but don't populate the Paragraph field
• Create a draft of EN version and enter content for the Paragraph
• As, expected, the published EN and SP version does not show the Paragraph, and the Latest revision of the source (EN) translation shows the Paragraph
• Edit the SP version and woops, the Paragraph does not show up and there's no way to add it.
• Publish the EN version. Now you can edit the Paragraph in the SP version

This gets worse when using an ERR field that is not a Paragraph. In this case, the ERR field does not show up in the SP translation even when the Latest revision is published. Of course, this is a separate issue.

Thanks for pointing out the other patch. Looks promising! But I'll stick with #18 here for now since it includes tests.

Ha cross-post with @catch. Was going to say that, the patch in #18 works well and I'll use it just to get the security patch on my customer' s site. However, I do agree with the patch and comments in #22 and #23 and will test that out as well. Although, I think it should probably have it's own issue.

The patch works in that the exception is no longer thrown. However, the block is still missing. Presumably because there are no links for ?

amaria → created an issue.

The patch in #12 works well for me.