Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
If you use a view reference within a field collection the field label displayed on the add/edit form is the same as the name of the parent field collection, not the field's label.
Rolling a patch...
Comments
Comment #1
srycroft CreditAttribution: srycroft commentedThis patch fixes the issue for me.
Comment #2
jamsilver CreditAttribution: jamsilver commentedI am also trying to use a viewreference field on an embedded subform on a custom entity type using the inline entity form (ief) module and it is also showing issues.
I have expanded the above patch to make viewreference grab the field settings and other data 'the right way' so it should always work.
Comment #3
jamsilver CreditAttribution: jamsilver commentedOK, I forgot to also copy this approach on the autocomplete process callback. Updated patch attached.
I've also added a second patchfile which applies cleanly on top of several of the other patches sitting on the viewreference issue queue.
Comment #4
klonosWetitling the issue title because it contained an ewwow. You should be caweful when typing weally fast. It's weally funny that @jamsilvew from ComputewMinds twyied to cowwect the title back in #2, but still missed that "w" thewe.
Also, I'm pwetty suwe the "(an field settings ignored)" part has a typo as well, but I don't know if you meant to wite "(any field settings ignowed)" or "(and field settings ignowed)"?
:D
Comment #5
mfrosch CreditAttribution: mfrosch commentedI used this module within inline entity form and also had the label problem.
Also the list of views wasn't filtered.
viewreference-1790304-03-complex-entity-form.patch worked for me!
thanks!
Comment #6
tannerjfco CreditAttribution: tannerjfco commentedI was encountering this issue as well as field settings not applying, which caused a handful of undefined index errors. Applying the viewreference-1790304-03-complex-entity-form.patch from #3 resolves the issue and the field is working correctly from within a field collection. I believe this patch is good to go :)
Comment #7
manu manuThe patch from #3 solved the issue for me too using Paragraphs.
Comment #8
manu manuChanged the title since Paragraphs items are affected too.
Comment #9
Softwar CreditAttribution: Softwar commentedThis patch #3 solved my problem with Multifield module.
I changed the title to add Multifield, just in case someone else has this problem.
Comment #11
danielb CreditAttribution: danielb commentedAlright, that took a bit of stuffing around to apply but I got there.
Comment #12
danielb CreditAttribution: danielb commented