Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Outer

Macro

MacrosStatusTested

Restrictions & Workarounds

Discussion
cachechart(warning)(tick)

Use the chart macro attachment parameters to persistently store the generated chart image so it can be displayed at a later time.

Another alternative is to put the cache macro inside the chart macro to save on the generation of the data from external sources while still doing normal rendering of the chart.

Normally, the chart macro creates a temporary image to display. The cache macro captures the html that references the temporary image. This displays properly as long as the temporary chart image is available. Once the temporary image is gone on the server, the chart can no longer be displayed by the another browser.

cache

expand or similar

(warning)(tick)

Reverse the macros - use the cache macro inside the expand macro.

Avoid using the cache refresh parameter. It will cause all the expand macros to contract since the expand macro does not remember the last setting.

Workaround is to put an expand macro somewhere on the page outside of the cache macro. See

Jira Legacy
serverJIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a-302c-339f-958b-015e107badcd
keyCACHE-75

The expand settings (expand or contract) are javascript based and not part of the html that is captured by the cache macro.

cachevarious

(warning)

 Some compatibility problems on Confluence 5.x due to
Jira Legacy
serverJIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a-302c-339f-958b-015e107badcd
keyCACHE-63
Workaround is to put the specific macro somewhere on the page outside of the cache macro (this brings in the resources necessary)
LegendStatus
(tick)Works
(warning)Works with some restrictions or workarounds
(error)Does not work in most cases
(question)Unknown

...