Thanks Nic. I'd rather not move assets around - it's one of the problems I'm trying to overcome, actually.
It's easy enough to compare dates programatically, I'm just wondering how to accomplish this within Squiz Matrix, to take advantage of the asset listing functionality.
Thanks Nic. I'd rather not move assets around - it's one of the problems I'm trying to overcome, actually.
It's easy enough to compare dates programatically, I'm just wondering how to accomplish this within Squiz Matrix, to take advantage of the asset listing functionality.
I didn't mean move the assets, just link them. I would link them into a location that has no webpath so that they don't get a new URL.
The individual pages listed will still need to be accessible, whether they are relevant 'now' or not. I should have stated that upfront. It's just the listing itself that needs to conditionally show assets.
The individual pages listed will still need to be accessible, whether they are relevant 'now' or not. I should have stated that upfront. It's just the listing itself that needs to conditionally show assets.
I realize that. But, by linking into folders like I mentioned you with effectively group them how you want. Then you can point an asset listing at those folders, list the assets, and the users will still be able to access those access through their normal URLs. The folders are just used to group the assets the way you are wanting and for the asset listing to source from.
1 - could you use conditions in a paint layout to decide whether a specific item gets listed or not? So the asset lister thinks its listing them all, but the format uses a paint layout where the whole output is in the test so it either prints the details or outputs nothing for each entry
2 - have the asset lister output the whole lot in a JSON array format - including the two dates - and then have a bit of javascript that tests the dates and dynamically adds (jQuery) the necessry HTML to a placeholder on the page for the ones that need to appear.