I cannot re-use an existing entity_reference_revisions field between two content types.
This appears to be because the no_ui parameter for the field plugin definition is set to TRUE. I don't know enough about this setting to know why it's set this way, but when I change it to FALSE, it seems to work okay for me. I'm using this with Paragraphs module, and it's now allowing me to add the field to a second content type. Data is storing, and I'm not seeing any errors.
I looked through the issue queue, and I think the setting got changed here: #2456281-14: Extend from EntityReferenceItem and remove redundant code Looks like it may have been unintentional, but like I said, I'm not sure of all the ramifications of this setting, so maybe not.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | entity_reference_revisions-2581413-2.patch | 881 bytes | zengenuity |
Comments
Comment #2
zengenuity commentedComment #3
jeroen.b commentedThanks!
Seems to be a change in core. They changed the way no_ui works.
Let's see if this patch makes it through tests.
Comment #5
jeroen.b commentedPushed to dev, thanks! Only issue I had with re-adding the same field is that it doesn't take over the widget settings, but that's a bug in core I guess.
Comment #7
jeroen.b commentedWeird...