Document Library page navigation

[darkredd]

Hello,

I recently upgraded to Community 5.1 the 201605 release, and have come to experience an issue. We have a lot of content in our repository, and when you open a folder that has say 20 document it only shows a few and there is not pagination buttons at the end of the page. Has something change that I need to configure or is this and error?

Help please.

[gawadesk]

Hi DarkRedd,

Ideally this should not be the case if upgrade process went smoothly. Anything specific issue/error during upgrade process or while indexation ? Did you checked log after accessing this folder ? Alternatively you can confirm number of documents in this folder by using Node Browser either by noderef or xpath.

Thanks,
Krishna

[darkredd]

Hi,

The upgrade went smooth without any error, there are no errors logged in the logs and I have confirmed the number of docs in the folder. What is shown is less to the number of documents in the folder.
My indexes are up to date and running as expected.

[gawadesk]

Hello DarkRedd,

In this case did you checked number of documents with Node Browser ? And is this behavior is for one particular folder or for multiple ?

To debug further you cam just write one test webscript to get all children of that particular folder and check number.

In worse case we have option to directly query in alfresco database to list down all children of that particular folder but will consider this option as last.

Thanks,
Krishna 

[darkredd]

Hi Krishna,

Thanks for your replies,

I had already gone through the steps aforementioned. All the documents are available and I can search on them and also the node browser can find them.

I thought perhaps it could be a bug or something I had missed to setup.

[gawadesk]

Hi DarkRedd,

Perhaps possibility of bug but should not be issue with setup.

If you have document in repository and you can see them via node browser and not through share interface that means it is issue of rendering. Only thing we can do is check metadata/status of those infected documents which may causing rendering of those documents.

Thanks,
Krishna  

[darkredd]

Hi,

The issue is throughout the entire system, not restricted to certain folders or file.
We only have custom metadata applied to a few pieces of content.
I am now inclined to think it is a bug. I will raise a JIRA ticket.

[gawadesk]

Hi DarkRedd,

Yes, JIRA ticket will be better. We only can figure it out such issues by looking into customization and details logs.

Thanks,
Krishna

[darkredd · Accepted solution]

Hi,

Here is the JIRA ticket:
https://issues.alfresco.com/jira/browse/ALF-21713