The listing has a type format for varieties and that also has keywords.
The folder and all images/varieties are live with public read access.
The listing is set to Down the Tree, with Driect Links Only "No" and no min/max depths.
The listing does not print out a single thing in relation to image varieties, even a preview of the image variety format yields no results.
If I change the root node to be one of the Image assets, the listing will print out the variety under it.
If I change the root node back to the folder or even the dummy site's root, and tell it to list images, they will (as expected) list.
So basically it is only printing out image varieties if it acts like "Direct Links Only" is enabled. Even when it's not.
Image variates are dependent on specific Image asset. They are shadow assets (not real assets that have its own url).
I don't think current listing page can handle mixing and listing them from a high level.
What you can probably do is that listing images first. And then nest another listing page in the format of asset content, to list current asset's children variates.
I'd only be wanting to list the singular image variety of about 20 or so images within the folder (as the root node).
I do not see (non-technically) why this would not be possible, however I accept that Squiz has made this choice.
I will try your proposed method, listing the image assets (perhaps name only or something) with the listing page for varieties inside the type format.
The reason I say type format is because I did not want to output a full-sized image, thus the trigger setting a variety to a certain dimension and then the vareity asset listing.
I'd only be wanting to list the singular image variety of about 20 or so images within the folder (as the root node).
I do not see (non-technically) why this would not be possible, however I accept that Squiz has made this choice.
I will try your proposed method, listing the image assets (perhaps name only or something) with the listing page for varieties inside the type format.
The reason I say type format is because I did not want to output a full-sized image, thus the trigger setting a variety to a certain dimension and then the vareity asset listing.
Thanks for your input and advice.
[/quote]
Why don't you just list the images then use an image variety keyword?
The technical reason is that image varieties are not assets and the asset listing only lists assets because it does DB queries over the asset table. It would take significantly longer to load the image assets as objects and determine their varieties to be able to list them, to the point of being unusable. It's not just a decision that was made.
I wonder if you can get around this by listing images, but putting image variety keywords in the type format. So instead of printing the image, you print one of its varieties. This allows the asset listing to find real image assets, but then asks the image to do the extra work to find the variety (if it exists) and print that instead.
[quote]
The technical reason is that image varieties are not assets and the asset listing only lists assets because it does DB queries over the asset table. It would take significantly longer to load the image assets as objects and determine their varieties to be able to list them, to the point of being unusable. It's not just a decision that was made.
I wonder if you can get around this by listing images, but putting image variety keywords in the type format. So instead of printing the image, you print one of its varieties. This allows the asset listing to find real image assets, but then asks the image to do the extra work to find the variety (if it exists) and print that instead.
[/quote]
Yes, Greg, I knew there would be a reason behind it. I just was not aware of the technical workings/problems.
I am mainly a front/back-ender with smaller CMS's so when I was introduced to Matrix, my mind imploded with all the DB queries it must be doing.
Thanks for the answer like Nic had stated. Much appreciated.
[quote]
Form and submissions folder all have public read permissions.
Is there a way to do this or should I use an asset builder instead of a form?
[/quote]
The form submissions/submissions folder have Public Read denied by default. Check the permissions of the folder to make sure this is not set. If it is, remove it, then add Public Read.
[quote]
The form submissions/submissions folder have Public Read denied by default. Check the permissions of the folder to make sure this is not set. If it is, remove it, then add Public Read.
[/quote]
Yeah I know. Thanks Nic but I did this before posting and still no cigar.
[quote]
Using /_nocache and /_recache on chrome and FF. No obstruction/squid cache layer.
[/quote]
When you removed the deny public read and added read did you cascade that down to the child submissions? Have you specifically checked the permissions of a submission?
