Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested Collections Parent/Child #118

Open
markprouse opened this issue Sep 12, 2019 · 2 comments
Open

Nested Collections Parent/Child #118

markprouse opened this issue Sep 12, 2019 · 2 comments

Comments

@markprouse
Copy link

markprouse commented Sep 12, 2019

Is it possible to have nested collections with Fluidity?

Persons
____|--> Person (fields etc)
____|--> Children
____________|--> Child (fields etc)
____________|--> Children
____________________|--> Child (fields etc)

If not natively, is there a work around which i can do achieve this using say three Collections so as i drill down each time i see the Children list and tabs for fields etc?

@mattbrailsford
Copy link
Owner

@markprouse not currently no, it's a long standing open issue #41. I'm hoping to spend some time on Fluidity next year for some big updates, but until I can focus on it, that won't be possible.

The only thing you can do right now is have them as separate collections and give the child items a parent picker property to pick the master entity. Then in the list view, created filters to filter by specific parent types. Not ideal, but best we have atm.

@markprouse markprouse changed the title Nested Collections Child/Parent Nested Collections Parent/Child Sep 12, 2019
@c9mb
Copy link

c9mb commented Sep 24, 2019

If you haven't already done so, then I'd recommend that before starting on big updates to Fluidity, you should download a trial copy of Sitefinity and check out the 'Dynamic Modules' function, for some inspiration in what Fluidity could be to Umbraco. Prior to being an Umbraco developer, I spent many years as a Sitefinity developer, and it was quite a step backwards to lose the functionality of something I'd simply taken for granted as a basic CMS feature. Of course, commercial software vs. open source is a challenge when it comes to matching feature-sets, and everyone makes their choices on where that trade-off needs to be, but it's good to know what's available in the marketplace and where the bar is set.

@c9mb c9mb mentioned this issue Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants