List view limit

Hi, just wanted to resurface this issue.

I found out that if you overlay /libs/wcm/core/content/sites/jcr:content/views/list to /apps/wcm/core/content/sites/jcr:content/views/list and change the values in 3 locations (limit, size, and datasource/limit), it seems to work great!

Just wondering if there are any downsides of doing this? Would it affect anything in View Mode on the Author instance? Is this purely for the Sites list view navigation? Would it slow any queries down? I'm assuming too that nothing would be affected on the Publisher since it's completely separate, but just throwing that question out there.

Thanks in advance!

Excellent response!

That's perfect, thanks!

I personally have never done that modification. I am not a big fan of adjusting the AEM user interface. However - let me check internally and see if anyone had done this. 

I figured that might be the case. We wouldn't normally endeavour to change something like this in AEM but since encouraging our content editors to move from classic to touch, there have been lot of comments about the siteadmin in touch. Most of the editors don't like the way the pagination works (i.e. adds more items as you scroll rather than having links to pick a page) so we were going to increase the limit and add more initial items.

Do you know how I'd find the resource type? I've tried changing /libs/granite/ui/components/foundation/layouts/listview but that doesn't seem to be doing much.

Adjusting the number of items displayed is not a configurable option. This will be a component - a resource type.  You will have to find that resource type and modify it. However, modify AEM scripts like this are not really best practice.