-
Bug
-
Resolution: Obsolete
-
Low
-
5.7.4
-
1
-
Severity 3 - Minor
-
Summary
When Page Properties macro is used to wrapped tables that have been generated with User Macro on a Confluence page, it then resulted in broken feature of Page Properties Report macro.
Note: This issue however is not reproducible in Confluence 5.4.3.
Steps to Reproduce
- Add a User Macro on your Confluence 5.7.4 instance that will then automatically generates a table on your Confluence page once it has been used, e.g. Preformatted Table User Macro.
- Include this Preformatted Table User Macro on your Confluence page.
- Add Page Properties Macro to your page that will then wrap the Preformatted Table User Macro.
Please be reminded to add a label to your page - you will need to specify this label in the page properties report macro. - Create a page to list all of the available Page Properties macro available on your Confluence space (this needs to be specified) by using the Page Properties Report Macro.
- Notice that the Page Properties Report macro is broken as per displayed in the attached screenshot (PagePropertiesObservedBehaviour.png).
Expected Results
Page Properties Report macro should be able to render all of the Page Properties macro once the label associated to that particular Page Properties macro has been specified in the Page Properties Report macro.
Actual Results
Page Properties Report macro is broken as per displayed in the attached screenshot (PagePropertiesObservedBehaviour.png).
- is incorporated by
-
-
- Closed
-
- mentioned in
-
Page Failed to load
[CONFSERVER-37847] Adding Page Properties Macro on Tables Generated with User Macro Resulted in Broken Page Properties Report Macro
I think the Summary of this issue gives the impression it is related to User Macros when it is actually related to anything that generates a table. Can you please review the priority of this?
Hi Atlassian, has there been any progress with this regression? We have a lot of broken tables.
@Mike Magargee, thanks for the tip about editing pages. Unfortunately it makes no difference on our server instance.
I also observed this and asked our IT group to file a bug report with Atlassian, In our instance, pages created prior to and running under 5.5.2 which contain the page properties macro and reported on a separate page containing page properties report worked just fine. Following an update to 5.7.4, the pages containing page properties report return "no content found" unless the pages containing page properties macro are edited. Pages edited after the Confluence upgrade to 5.7.4 then report as expected in the page properties report. But pages that were not updated do not. This is unacceptable for our needs and I am probably going to dump the page properties report in favor of Service Rocket's reporting macro. That approach does not suffer from this problem.
Mike Magargee
There is no workaround that I have identified for this issue. On upgrade of Confluence, any generated table currently in a page-properties macro will fail to appear in the page properties report. I think the priority should be higher as a result.
Note this issue occurs with common addons, such as the Bob Swift SQL addon which returns data in a table.
Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket.
If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review.
You can read more about the editor upgrade in the 6.14 Release Notes.
Thanks
Makisa Appleton | Senior Product Manager, Confluence Server and Data Center