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.

Comments

zengenuity created an issue. See original summary.

zengenuity’s picture

StatusFileSize
new881 bytes
jeroen.b’s picture

Status: Active » Needs review

Thanks!
Seems to be a change in core. They changed the way no_ui works.
Let's see if this patch makes it through tests.

  • jeroen.b committed b30a561 on 8.x-1.x authored by zengenuity
    Issue #2581413 by zengenuity: Cannot "Re-use an existing field" with...
jeroen.b’s picture

Status: Needs review » Fixed

Pushed 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.

Status: Fixed » Needs work

The last submitted patch, 2: entity_reference_revisions-2581413-2.patch, failed testing.

jeroen.b’s picture

Status: Needs work » Fixed

Weird...

Status: Fixed » Closed (fixed)

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