Facing same issue on 7.13.3

Hi,

 I also facing the same issue for version 7.13.3, can somebody help me with this?

Thanks.
Hisham

This issue is present 6.6.6.

Hi, can you reopen this ticket. We are using Confluence Server 6.3.4 and the issue is still there. User mentions in page properties macro break it.

Don't do that in production. If you are really curious then try it out in a dev/test environment. From my experience using a jar file for another version does not seem to work well in Confluence. YMMV.

Hi Denise,

We are now also hit by this issue on a Confluence 5.9.10.

Is there any negative side effect if replace the old jar with the latest 5.0.7? https://marketplace.atlassian.com/plugins/confluence.extra.masterdetail/versions says it's for Conf 5.10.0 onward. However, we cannot update right now.

This issue has been resolved in Confluence Cloud, and in Confluence 5.10.4 which is now available for download.

Same here. We also would need this update!

Same here. 5.9.x version needed. Thanks. 

Same here. We would need this update for 5.9

Doesn't work with 5.9.x Release. As we cannot upgrade to 5.10. by now, please also fix the 5.9 version, as the issue occurred in this release first.

This issue has now been fixed. The fix will be avaliable in cloud shortly. Server customers can download version 5.0.6 of the Page Properties plugin to get the fix: https://marketplace.atlassian.com/plugins/confluence.extra.masterdetail/versions

mfalcone224395166 Our sprint is one week. You don't need to do anything. We'll release a new version of the plugin and give out the download link so that server customers can install it without having to wait for the next server release.

Our Senior Management rely on this information and my team has spent countless hours trying to get the information to them because of this bug.

I am so happy to see this is in a sprint now, how long are your sprints and what do I need to do in order to get this to become a higher priority?

Any update to this bug?

+1

Is there a workaround for this issue? It is a blocker for our teams.

Any updates on this?

we have the same issue displaying pages which only contain Text, Status and Page Information Macros.

Sent you an e-mail.

We get this error with EVERY browser (IE, Chrome, Firefox latest versions). Confluence 5.9.11!

If it's not confidential, adding it here wrapped in a {code} macro would be preferable. Otherwise, feel free to send it over via email.

A self made template and page properties report to show them. We're not using JIRA issues in there. You want me to send you the source of the page(s) to your e-mail?

Please note we only experience this on IE, not on Firefox / Chrome.

patrijst what content do you have in your page properties?

I've been able to reproduce the error when including the JIRA Issues macro, but not when using status macros and text only.

Same here, IE11, Confluence 5.9. We're using Themepress as well.

Hi, We did a test and the problem still persists. When using f.ex the JIRA Issues macro the proplem with pagination occurs as well. This means that it is not only a fault of some third party plugins. Confluence Server 5.9.6.

Monique, Unfortunately, the problem persists for us in Plugin Safe Mode. We are currently running Confluence Server 5.9.9.

Dear All,

I have discovered a similar bug that was caused by certain third party plugin such as

• Comala Workflows v4.12.2
• Page Information for Confluence by Adaptavist, v3.2.8

As per mentioned by Michał J. Sładek and Keith. After disabling the plugins above, I've discovered that the "2nd page" in the page properties report macro works normally. This was discovered in Confluence v5.9.8-5.9.10

Please check if there were any third party plugin involved in the "Page Properties" macro, and if there were, please do comment and let us know which plugins that are affecting the "Page Properties Report" macro. The easiest way to check is by Enabling Plugin Safe mode and check if the Pagination works afterwards.

Please do comment on the following bug report if this is true:

• https://jira.atlassian.com/browse/CONF-42669

Kind Regards,
Monique

We need to get this issue fixed asap.

Please correct this bug. Our business uses the Page Properties macro a lot throughout Confluence, and we display things like Status macro, JIRA issues, etc and right now they are broken.

This is also CRITICAL for us. I was assured that this will also fix another issue with non plain text attributes: "All issues with the pagination of the Page Properties Report macro are being treated in this bug ticket. Currently, the macro has issues with pagination when the properties are not plain text, which is the case for you as you are using images. Gathering issues with the macro in a single ticket will help developers to fix all unwanted behaviors without missing one, and deliver one general fix to all Cloud instances". I hope you will fix this soon.

This is an issue on Confluence 5.9.9

This is core functionality for Confluence. Why would you leave a bug in your core product for so long? I'd love to hear from the development team.

I can also confirm that the problem appears once you use a macro as page property value (e.g. Status, Page Information)

It seems that it is working when the Properties are just plain text. When some HTML is send then it is not working f.eks Status macro in our case. When we took out the Status column then it worked as expected. Hope it can help someone of you.

I can confirm that pagination is not working properly.
We have similar findings as reported by Jan-Peter Rusch above.

I wondered wthether it would be possible to completely switch off pagination for the moment - just showing a very big list. However, it looks like this is not possible.

The same feelings out here. Our users are also very confused and are asking every day for a working solution or at least a workaround for this issue.

Update: 5.9.7 still affected (Confluence Server 5.9.7 Windows 64bit Installer). You can't even page back to the first page. After one pagination event the report is empty. Our users are really p***ed by now. My support call was closed with result "Existing bug". Well, I knew that, but a little bit more effort was expected. Any update, if this will be fixed with the next release?
This issue renders page properties reports unusable.

I can confirm this CRITICAL issue with 5.9.6 & will open a support call with Atlassian.

Sadly, there is no workaround as setting the number of object to display to a high number. This parameter is ignored, if set to higher than 30.

As we are handling control lists spread over several spaces with this macro, the issue is a complete blocker for users working with these lists.