Asset listing only renders when nested in standard page

Squiz Matrix Support
1

Hello all

 

I have an asset listing which will not render if requested directly - not only does the whole body design area fail to render, but nothing else after that point in the parse file appears in the generated code of the page - nothing from the paint layout or design.

 

However, if I nest the asset listing in a standard page, it works fine. What am I not understanding?

 

Thanks

 

Tom

2

May be irrelevant... but the only times I've found huge chunks of a page failing to render was when I've accidentally missed out a closing % on one of my keywords

3

Yea check out the formatting of the type format on the asset listing, try stripping it back and just printing something dead simple like %asset_position% and see if that works. 

 

How many records is the asset listing printing? I've also found that if the listing is too big and too big of a hit on the memory of the server, it would stop producing HTML on the front end at a random place in the listing. 

4

> missed out a closing %

 

Well, I've checked, and they are fine. Plus, if that was the issue, then the asset listing would not render when nested.

 

> How many records is the asset listing printing?

 

One. I'm just building the site now. Plus, the same counter-argument applies: why would it fail when requested directly, but work when nested?

 

Baffled.

5

Does your asset listing and the designs folder have the same Web domain/URL?

6

In a word, yes.

7

For the moment, I'll have to nest it. An extra layer of unnecessary complexity, but it works. If someone figures it out, let me know.

8

Plus, the same counter-argument applies: why would it fail when requested directly, but work when nested?

 

It could fail when requested directly because it would be also printing a Design and maybe a paint layout.

 

If you nest it, the Design and most likely the paint layout would not be printed. Only the contents of the asset.

 

So, my guess is the Design and the Paint Layout are what is causing the page to break.

9

The explanation was my fairly basic ignorance of Matrix. The asset inherited a paint layout which only had a standard page type format defined. Adding a type format for asset listing page sorted it. Obviously.

 

Thanks

 

Tom

10

The explanation was my fairly basic ignorance of Matrix. The asset inherited a paint layout which only had a standard page type format defined. Adding a type format for asset listing page sorted it. Obviously.

 

Thanks

 

Tom

 

That is still strange though. Paint Layouts always have a default format. I do remember however that in really old versions of Matrix that the default format did not print the asset_contents keyword by default...But I mean really old versions. Like 3.16.

11

Ah, but what if an uninformed user had deleted the default format, leaving only the standard page one?

12

Ah, but what if an uninformed user had deleted the default format, leaving only the standard page one?

 

Ha, well that would be the issue then. :)

13

My oops. Thanks, everyone.