Multiple Page Asset - thoughts on replacement options?

Squiz Matrix General Discussion
1

We have a few sites using multiple page assets which are deprecated from v5.1.0 (

 

Anyone have replacement options that they want to share?

2

you could probably knock together an equivalent with standard pages & a paint layout/asset listing?

3

It's possible to achieve a flexible solution utilising asset listings, paint layout and the JS REST asset. At a high level the solution is:

  • 1 asset listing configured to look up the tree 1 level listing only one asset (this is used to get the parent asset)
  • 1 asset listing to look down the tree 1 level and nested inside the previous listing with a root node using the session variable 'list_current_asset_id'. This listing is configured to produce JSON formatted list of the siblings of the currently viewed asset.
  • Paint layout that displays the page contents along with the contents of a JS REST asset that is configured to output a list of sibling pages for pagination. The JS REST asset contains logic written to output the appropriate pagination markup for next/previous and current page. Here the 'REST' part of that asset has no functionality, it's simply used as a container to run server side javascript (by default V8) on Matrix keywords.
  • You would normally combine this with a reasonably aggressive cache strategy to avoid all those listings & server side JS from executing on each page load.

If you get in touch with your local Squiz representative we have some pre-developed solutions (a.k.a 'scaffolding') you could use as a starting point for this.

4

Hi all,

 

I'm looking at replacing our multiple page assets, so that we can plan to upgrade to 5.2.x

 

In the manuals I've found the keyword replacements %asset_sibling_prev% and %asset_sibling_next% which I'm thinking that combined with the keyword modifiers as_asset:asset_href and as_asset:asset_name could be used in a paint layout to display  next/previous links, for a collection of standard pages.

 

<a href="asset_sibling_next^as_asset:asset_href">asset_sibling_next^as_asset:asset_name</a>

 

Unfortunately these keywords were added in 5.2.0 and so can't be tested in 5.1.x.

 

Would these keywords replacements work to create next/previous links?

5

 

Would these keywords replacements work to create next/previous links?

 

I think that was the idea behind creating them, to avoid the complicated solution I posted above. My information is a bit old - it's now possible to do almost the exact same thing just with those keywords you mentioned (5.2+).

6

This is great news, the only problem is that the keywords aren't available to use until 5.2 at which time the multiple page assets cease to function.

 

Georgina.