When doing a 'standard' sort with a limit of X items per page.
This feature does not work when under construction.
Works fine when asset is live.
Bug or intentional functionality?
Forget the first paragraph. Incomplete testing…
If you set up a date range on the details page it displays fine in sets of X.
If you set up date ranges for the user to select, then it breaks.
Again… Bug or intentional functionality?
- Intended functionality. Asset Listings (and things that inherit, i.e. What's New and Search) only display live assets in v3.4.x.
- Intended functionality. You need to configure at least one date range on the details page. Additional date ranges are then made available to the user via a keyword replacement in the Page Contents bodycopy. This prints a drop-down list of ranges the user can select from.
Thanks Avi,
I think you missed my point. You explained the functionality of the page fine. I know this.
The problem is…
A. You create the additional date ranges for the user to select.
B. You set the page up to display only 10 assets per page.
C. User logs on.
D. User sees nice page of 10 assets and navigates happily from page to page
each containing 10 assets.
C. User selects last months list of assets.
E. User presented with list of not 10 but 120 assets on one page.
Yup, that's Intended Functionality too. The list doesn't paginate once a specific date range is selected. That's how the original client wanted the page to work.
If you want each date range to paginate, it'll require development.
Thanks Avi.
We can live with it as it is. Just wanted to check that was the way it was intended to be.