When adding a Page Properties Report macro to a page, pagination breaks when a large number of items is included in the table. I have a page with one of those macros that returns roughly 200 items (resulting in 7 pages of 30 items each). When the container page is displayed, the first 30 items in the table are shown properly. However, when I click on the "Next" button at the bottom of the table, said table empties and the next 30 items fail to show even after a considerable wait.
Does anybody know what's going wrong?
We are using Confluence 6.0.0-OD-2016.08.2-0008 hosted by Atlassian.
I am having the same issue as described here. Updating the Number of items to display doesn't seem to make a difference either.
In attempt to display all of the items on the first page I tried to enter in 200,100,50 and the initial page is limited to show 30 items after each attempt. Following pages accessed via next or the page number itself still fail to show.
I'm using Confluence 6.0.0-OD-2016.12.1-1106
Related link - https://answers.atlassian.com/questions/37058620
Coming back to this, I was able to implement a workaround for me that avoids the pagination:
Steps I used:
Note that updating the Number of Items to display after already inserting/saving the macro with the default at 30 doesn't fix the pagination issue
Doh! Apologies if my workaround has confused things.
I'm not sure what the difference may be as I am still able to create new pages with the macro not being limited to 30 items using those steps. If its a new page I just have to do step 4.
I'm using Google Chrome if that adds anything
Ok sweet the new page version did work! If i create a new page and the 1st thing i do before saving (creating the page) is to add the macro and set the results to 2000 it did work. adding it to an existing page always sets it to 30. Using Server v. 5.9.12
Ok i take that back. I occasionally can get it to "work" but it only show the page titles. It appears that once it shows the details from any additional columns show, it reverts back to 30. Thanks for the hint, i guess i will just need to wait until its actually fixed. For now i will have to break up the content into sub reports with less than 30 if i want to avoid paging.
Yay! Glad I'm not the only one it works for. Thanks for the update John
Ah ok yep I see what you mean. I have the same issue - for now they are working for me as I have limited reports to what is in the page properties and only tallying the comments/likes on the page.
Hopefully the bug is fixed soon cause I can imagine the sub reports could get a bit cumbersome to maintain?
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs