[magnolia-user] Re: 2-levels Content App

2016-07-12 Thread Matteo Pelucco (via Magnolia Forums)
Thanks Jan, I'll try asap and let you know. I missed the "setting root path dynamically while oppening subapp is showcased in neat-config app btw :D" :) -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=58da7f6a-1f75-4ba3-bb3f-1ee4d82c8d31 ---

Re: [magnolia-user] Re: 2-levels Content App

2016-07-12 Thread Jan Haderka
Should be rather simple no? “Show books” action will open second subapp with “root path” set to the author on which action was invoked. That way you have view limited to just the books and can have different column formatters shown. (setting root path dynamically while oppening subapp is showcase

[magnolia-user] Re: 2-levels Content App

2016-07-12 Thread Matteo Pelucco (via Magnolia Forums)
Hi Mika, got your point, you are assuming to show both types on the same app, hieararchically. What I would like to achieve, is similar to Sitemap App. VIEW1: Authors [code] | FirstName | LastName | DateOfBirth | ... | | | | ... | John | Grisham | 19xx.xx.xx

[magnolia-user] Re: 2-levels Content App

2016-07-11 Thread via Magnolia Forums
Hi Matteo, Assuming you want to edit books individually, with their own form. In the old days when migrating the data module to M5 (company app sample was similar node-type-wise), we had one custom action building the correct DetailLocation based on configured "sub-app mappings". Nowadays (sin