Hello, while playing with Relation field parameters and template settings, I noticed a "limitation".
Issue:
How to change the children display in Records module? Independently from list view template.
Obviously, the module itself has a parameter for the parent records template. But how to deal with their children... it seems to use the same setting from the parent field parameter: "Show Children". So, the module gets the same children appearance like the list-view.
Workarounds: I would have to make a generic layout that fits into both contexts. List view AND module. Difficult, because of limited space and different infos in module context. Maybe modify module template appearance with specific CSS... most likely not a solution for TABLE-based markup. Maybe easier for DIV, UL/LI markup...
Question:
Does it make sense to have an additional parameter to distinguish between list/full and module context? I remember, you have done something similar for fields filter template: You added a "template for filter module" parameter.
Suggestions / Thoughts:
- Additional Module Template parameter in Parent field -> Show Children ?
- Is it possible to override children template in module? Additional parameter "Template for childs" in Records Module ?
Idea
Announcement
Conversation
Praise
Problem
Question
Reviewed
Open
Hello, while playing with Relation field parameters and template settings, I noticed a "limitation".
Issue:
How to change the children display in Records module? Independently from list view template.
Obviously, the module itself has a parameter for the parent records template. But how to deal with their children... it seems to use the same setting from the parent field parameter: "Show Children". So, the module gets the same children appearance like the list-view.
Workarounds: I would have to make a generic layout that fits into both contexts. List view AND module. Difficult, because of limited space and different infos in module context. Maybe modify module template appearance with specific CSS... most likely not a solution for TABLE-based markup. Maybe easier for DIV, UL/LI markup...
Question:
Does it make sense to have an additional parameter to distinguish between list/full and module context? I remember, you have done something similar for fields filter template: You added a "template for filter module" parameter.
Suggestions / Thoughts: - Additional Module Template parameter in Parent field -> Show Children ? - Is it possible to override children template in module? Additional parameter "Template for childs" in Records Module ?