Question about new features

[nnhubbard]

I was reading the newsletter, and saw the new features for the listing engine. Could someone explain them a little more, and when they would be used? I am most curious to know if these are the fixes to the nested asset listing with paint layout, nested inside another page, which could be nested inside another page(unlimited number of nests). I remember Avi saying someone submitted a fix for this, and was not sure if this was it.

[quote]- Listing Engine assets now expose a new "Session" dynamic parameter variable, "list_current_asset_id". This can be used in a nested asset listing (or theoretically, any other asset that supports dynamic parameters) to use the asset ID currently being listed as the input into a dynamic parameter.

• Asset Listing Page assets now have a new dynamic parameter that essentially acts as a "Replacement Asset IDs to Include" option. If this dynamic parameter is specified, then the full list of assets that would normally be listed are replaced with this replacement list.[/quote]

[Avi_Miller]

I am most curious to know if these are the fixes to the nested asset listing with paint layout, nested inside another page, which could be nested inside another page(unlimited number of nests).

Yes, this is it. Essentially, it means you can nest an asset listing (B) into the Type Formats bodycopy of another asset listing (A). Then, you'd set a Dynamic Root Node Parameter for B to the Session Variable "list_current_asset_id". Asset Listing (A) will set this variable each time it calls the Type Format bodycopy, so Asset Listing (B) will change its root node appropriately.

[nnhubbard]

Yes, this is it. Essentially, it means you can nest an asset listing (B)’ /> into the Type Formats bodycopy of another asset listing (A). Then, you’d set a Dynamic Root Node Parameter for B to the Session Variable “list_current_asset_id”. Asset Listing (A) will set this variable each time it calls the Type Format bodycopy, so Asset Listing (<img src=‘http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/cool.gif’ class=‘bbc_emoticon’ alt='B) will change its root node appropriately.

I take it that a client must have pushed this along, as last time I heard this feature was not going to be added for some time, at least that is what I thought..

[gsherwood]

I take it that a client must have pushed this along, as last time I heard this feature was not going to be added for some time, at least that is what I thought…

No, we just found the time to apply and test the patches.