Hi Top,

I believe the best solution is for the Page Properties report macro to issue an event in the same way that the JIRA filter macro does. When the macro is done loading a completed event is issued that we can listen for and react to.  If the macro fails then it can issue some failure event as well.  This is the pattern I was suggesting be followed by all asynchronously loading macros. 

is that what you were asking for? 

Thanks!

Hello Jeff,

So,what is your real solution?

Best regards
Top

We have a similar issue on Advanced Tables on Confluence Cloud as well.  Hopefully, similar solutions can work there as well.  Thanks! 

As mentioned above with the Page Properties Report macro the contents are loaded asynchronously.  This causes a problem for the Advanced Tables code because it does not know when to run.  Upon investigation, we have been unable to find a reliable method to determine when it's done.  We have looked at different mutators and events.  

We had a similar issue the JIRA Filter macro in Confluence.  It now loads asynchronously.  However, we were able to find an event that we can bind to when it's completed (AJS.bind('confluence.extra.jira:jira-table:completed.success'...).  However, there does not seem to be such an event for the Page Properties Report macro.  This seems to be a pattern that should be required to be followed anytime Confluence changes the behavior of a macro such as this.  

Is this something that can be considered?  

Thanks! 

Jeff

As Manoj Akondi said,

We are also using Atlassian products and We are facing the same issue when we use "Page Properties Report" with "Table Plus Macro". The page is stuck at "Generating page properties report..".
But it works when we add "?&pagepropertiesreport.serverrender" at the end of the page URL. They page renders just fine.
This ticket has been created for a long time.
We have no doubt that atlassian team is professional,so we wish someone could resolve the issue asap.

Best regards
Top

We are using Atlassian products and We are facing the same issue when we use "Page Properties Report" with "Table Plus Macro". The page is stuck at "Generating page properties report..".

But it works when we add "?&pagepropertiesreport.serverrender" at the end of the page URL. They page renders just fine.

We have many users reporting that they are facing issues with using this with "Table Plus Macro". Please resolve this asap.

Klaus, thanks for the info. It is good to know the awareness is there. Some acknowledgements along the way are helpful for followers.

Hello,

We are aware of this issue but unfortunately do not have the capacity to fix it in the short term but we'll try to look into this later and get this fixed.

Apologies for all the inconvenience.

Thanks Bob! I've actioned your suggestion. We'll have to wait and see what comes of this.

Yes, I know . You pretty much have to go through Atlassian support and point to this issue, then escalate ... . It seems to be the only way to get some attention and then it will still take a bit to get it queued.