Notice: The foo bundle was deleted. As a result, the bar entity reference revisions field no longer specifies a specific target bundle

Is there any solution here to avoid this ? I get this too.
I have a multisite setup (2 sites), site one has a quiz content type and a field that references a quiz_answer paragraph.
Since the site 2 doesnt have that content type and doesnt have the paragraph, i added this to full split.
I do a
drush @project1_alias si --existing-config -y
than
drush @project1_alias cex
and i get this notice
[notice] The Quiz answer bundle (entity type: paragraph) was deleted. As a result, the field_paragraphs entity reference revisions field (entity_type: node, bundle: quiz_question) no longer specifies a specific target bundle. The field will now accept any bundle and may need to be adjusted.
When i login to the backend everything seems fine.

Yep this message is occurring due to config split. The implementation in \Drupal\entity_reference_revisions\Plugin\Field\FieldType\EntityReferenceRevisionsItem::onDependencyRemoval() is incorrect. This method cannot log a message at this point because it has no idea if this will occur on not. The config system can do a dry to determine what entities will change when you remove one. Config split uses this to determine is config needs to be split.

The fix here is to move the message to post save hook and set a flag in the onDependencyRemoval() method. Or something like that.

Also in the most basic usage of the entity reference revisions this message is actually wrong.

If you follow these steps:

• install standard
• Enable entity reference revisions
• Create a node type called Test
• Create an entity reference revisions field on Article and let it reference nodes of the type Test
• Delete the node type test.

Then view the log messages you will see 3x the message from \Drupal\entity_reference_revisions\Plugin\Field\FieldType\EntityReferenceRevisionsItem::onDependencyRemoval
The Test bundle (entity type: node) was deleted. As a result, the field_err entity reference revisions field (entity_type: node, bundle: article) no longer specifies a specific target bundle. The field will now accept any bundle and may need to be adjusted.

Then you will see the following message from the field module
The field_err entity reference field (entity_type: node, bundle: article) no longer has any valid bundle it can reference. The field is not working correctly anymore and has to be adjusted.

The last message is correct in this situation. My guess is that the message might be true for certain handlers but it is not true for the default handler provided by core. I think the correct thing to do here is to remove the message from entity_reference_revisions and if it is true with the handler from paragraphs then do something there because atm this message is wrong more often than it is correct. Note if you cancel deleting the content type Test during the delete you will still have 1x the message in the log because of the dry run.

If we really want to add this message then we need to copy the field module and do something in hook_field_config_presave() or hook_field_config_update() but as detailed in #7 I'm not sure about this.

This was initially copied from core, which moved it in #2925913: EntityReferenceItem logs critical errors in onDependencyRemoval() → . field_field_config_presave() also acts on ERR field types, which I'm not sure is really desirable(it explicitly supports subclasses of EntityReferenceItem) but considering that, it seems fine to remove it.

Also, \Drupal\Core\Entity\EntityDisplayBase::onDependencyRemoval() is a similarly flawed remaining case in core that still logs stuff in onDependencyRemoval().

You're likely also getting this message on the manage permissions page of such a target bundle, see 🐛 Don't hide permissions local tasks on bundles when no permissions are defined Needs work (I may or may not be trying to lure @alexpott towards that issue)

Merged.

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