The dependent field functionality passes an entity ID to the user-supplied view. If the user set up the parent argument (i.e. contextual filter) as one that accepts UUIDs instead of entity IDs (e.g. Taxonomy term: UUID), the functionality breaks, and as a result, the dependent field options list becomes empty.
To add support for UUIDs as well, which are portable across sites (unlike entity IDs), we can pass in the UUID instead of the entity ID if the user chooses this option.
I don't believe there a good way to deduce how the user set up the argument. As such, I think we need a configuration option for this. A checkbox should be sufficient.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | business_rules-parent_argument_as_uuid-3117868-3.patch | 9.42 KB | colan |
| #3 | interdiff-3117868-2-3.diff | 7.05 KB | colan |
Comments
Comment #2
colanWe still need to implement the update hook to add the new configuration option to the existing configuration.
Comment #3
colanThis should do the trick, but more testing would be nice.
Comment #5
colanRetested with a clean site update. Works well & doesn't cause any problems.
Comment #7
colanThe form can't be submitted if this functionality is enabled with the
Reference parent by UUID instead of entity ID?checkbox even though the field selections work fine. See #3137122: Referencing parent by UUID prevents entity form submissions for that issue.Comment #8
colan