If I explicitly designate the 3.x version in composer.json, the issue goes away.
composer require 'drupal/dynamic_entity_reference:^3.2'
I just experienced this issue on many of my Pantheon instances, and I was extremely concerned about how I'd rectify the issue on local/multidev/dev/test environments over the course of our project. AFAIK, the issue seems to be endemic to the 4.x version. I didn't seem to see any explicit notes re: the 4.x build hosting this issue, so I'm hoping this note helps someone.
Hat tip to this post → for pointing me in the right place.
Ah, right you are. I misread "Migrate Conditions" as being a write-up of the existing migrate conditions, but now I see that it's its own module. Apologies for that.
Maybe I'm missing something, but I'm not seeing `skip_on_condition` on 10.2.3. Has this process plugin been removed in later versions of Drupal?
coconnor → created an issue.
Can confirm this is an issue.
Also may be worth noting that we see the same behavior when you set the entity reference revision to "require on publish"
To reproduce:
- Make sure workflow moderation is set up on your content type
- Add a regular field to your content type.
- Add a paragraph ref field to your content type - using field type 'Entity Reference Revisions'
- Mark the regular field as 'Required on publish'.
- Mark the paragraph ref field as 'Required on publish'.
- When you go to add a new node and you'll see the visual indicator (blue triangles) on both the regular field and the paragraph field, but only the regular will be required to publish.