I've set up a Simple Edit Layout for Multi-date Events, and within the layout I would like to nest an Asset Listing to display the Multi-date Event's child Single and Recurring Event instances. For each of the listed instances I want to include links to let an author go off and edit that particular event, etc.
So with the Asset Listing I'm trying to set it to use the parent Multi-date Event's asset ID as a dynamic Replacement Root node. I've tried setting the dynamic parameter with Current Asset set to Asset ID, and separately (i.e. not at the same time) with GET Variable Name set to %asset_assetid%.
However, when I do either of these things and then try to call up a Multi-date Event's simple editing form, any content situated above the nested Asset Listing displays okay, but instead of the nested listing I get nothing but a bunch of error messages starting with:
Fatal error: Uncaught exception 'Exception' with message 'Assertion failed: [NULL] "" is not a valid asset ID' in /var/www/slq3223/core/include/assertions.inc:507
It appears that it's not able to find the dynamic root node and throws a Fatal error as a result.
I've tried it with the Asset Listing set to use just the static root node, but I get the same Fatal Error as a result. I've also tried applying a Paint Layout with the nested Asset Listing in it to the Simple Edit Layout, but of course it didn't work either, and just displayed my keyword, %asset_contents_paint_189328%, instead of the form's contents.
So maybe it's not actually possible to nest an Asset Listing in a Simple Edit Layout? Or am I doing something wrong in my set-up process? Has anybody else experienced this problem, and perhaps found a way to solve it?
Thanks for any assistance. We're using version 3.22.
[quote]
I've set up a Simple Edit Layout for Multi-date Events, and within the layout I would like to nest an Asset Listing to display the Multi-date Event's child Single and Recurring Event instances. For each of the listed instances I want to include links to let an author go off and edit that particular event, etc.
[/quote]
Sounds interesting, never tried this myself. I do know tha Multi-date event asset works quite differently than most other assets when it comes to its 'contents'. I'm not sure the event instances are even shadow assets (need developer input) so I would not have thought you would be able to list out anything of use for editing individual instance i.e. they dont have URLs and I was unable to get limbo references working, although I only just ran a very quick test.
[quote]
However, when I do either of these things and then try to call up a Multi-date Event's simple editing form, any content situated above the nested Asset Listing displays okay, but instead of the nested listing I get nothing but a bunch of error messages starting with:
Fatal error: Uncaught exception 'Exception' with message 'Assertion failed: [NULL] "" is not a valid asset ID' in /var/www/slq3223/core/include/assertions.inc:507
[/quote]
What is the current config for your asset listing details screen? Do you get the same error when trying to nest a standard page asset, or an asset listing configured to list links to standard pages under a static root node?
Most of my 'simple edit' work latest has been EES and/or Jaxifying simple edit layouts (content output from dynamical requests/respones via JS) sounds like you have set yourself a solid challenge with simple editing the multi date event. That particular asset was developed along time ago for a specific use case and I believe has had little changes sinces, you can't even return matrix search page results from that asset.
Let me know how you go, or what solution(s) you come up with if any.
Cheers
Scotty
Have you tested it to see if this method works outside of simple edit?
[quote]
Sounds interesting, never tried this myself. I do know tha Multi-date event asset works quite differently than most other assets when it comes to its 'contents'. I'm not sure the event instances are even shadow assets (need developer input) so I would not have thought you would be able to list out anything of use for editing individual instance i.e. they dont have URLs and I was unable to get limbo references working, although I only just ran a very quick test.
What is the current config for your asset listing details screen? Do you get the same error when trying to nest a standard page asset, or an asset listing configured to list links to standard pages under a static root node?
Most of my 'simple edit' work latest has been EES and/or Jaxifying simple edit layouts (content output from dynamical requests/respones via JS) sounds like you have set yourself a solid challenge with simple editing the multi date event. That particular asset was developed along time ago for a specific use case and I believe has had little changes sinces, you can't even return matrix search page results from that asset.
Let me know how you go, or what solution(s) you come up with if any.
Cheers
Scotty
[/quote]
Hi Scotty,
I do indeed get the same error messages when I try to nest an Asset Listing with a static root node, and when I try nesting a Standard Page - so it sure looks like it's simply not technically possible to make it do what I want.
Never mind. I think for the moment I'll simply include a link in my form to a separate, non-nested Asset Listing and pass it the Multi-date Event's asset ID dynamically. That seems to work okay, so it'll have to do. Perhaps one day Squiz will get around to doing some more work on the Layout and make nested content possible with it. (I haven't tried nesting content in Layouts for other asset types - I'll have to try it and see if this is a broader problem, or unique to Multi-date Events.)
Thanks very much for the feedback and suggestions.
Steve
[quote]
Have you tested it to see if this method works outside of simple edit?
[/quote]
Hi Nic,
I've been able to successfully nest a dynamic asset listing in a Paint Layout for Multi-date Events, such that when you view the event's page, you see entries for its child Single and Recurring Events listed within the rest of the page contents.
So it certainly works okay for Paint Layouts, which is why it came as something of a surprise that it doesn't work with Simple Edit Layouts.
Cheers,
Steve