When I create a view that is based on a content type, but let's say this content type has a field collection in it, and this collection has 2 entities. This might be the same deal with any multi field, I'm not sure, but either way, the view ends up getting two rows, with the same node ID, which is all according to plan. Let's say then that the megarow field in the view will load up another view, injecting the entity ID from the multifield.

What then happens is that BOTH ROWS expand. The first row, is the only row that accepts editable field input, the other row is simply dead for any input, and the result that I expect shows, it shows on BOTH ROWS.

Something is weird with the ajaxification here, but it's beyond me to repair it..

Comments

ibuildit created an issue. See original summary.

andrii momotov’s picture

andrii momotov commented
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.