Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

Summary

The cache Cache macro works fine well with many macros, however, there are cases that you may need to order your macros carefully in order to get the desired expected results. The cache macro will not help with Cache macro does not support macros that use javascript asynchronous approaches to bring data into a page. This is because the cache macro Cache macro caches the rendered HTML content, which in that case is just a place holders holder for data that then still needs to be brought in. 

See Future Macro macro - Interoperability for interoperability with the Future Macromacro.

This page is intended to document interoperability with other advanced macros. Please comment or report on other interoperability problems. 

Outer

Macro

MacrosStatusTested

Restrictions & Workarounds

Discussion
cachechart(warning)(tick)

Use the

chart

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

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

Chart macro creates a temporary image to display. The

cache macro

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

(tick)(tick)

Reverse the macros

-

use the

cache macro

Cache macro inside the

expand

Expand macro.

Avoid using the

cache

Cache refresh parameter. It

will cause

makes all the

expand

Expand macros

to

contract since the

expand

Expand macro does not remember the last setting.

Since 6.1, a workaround has been implement to make the expand macro work inside

a cache

Cache macro pending full availability of Confluence 5.4.3 (see CACHE-75).

cache

expand or similar

(tick)(tick)

Reverse the macros

-

use the

cache macro

Cache macro inside the

expand macro

Expand macro.

Avoid using the

cache

Cache refresh

parameter

 parameter. It

will cause

makes all the

expand macros to

Expand macros contract since the

expand macro

Expand macro does not remember the last setting.

Prior to 6.1, workaround is to put an

expand macro

Expand macro somewhere on the page outside of the

cache macro

Cache macro. See

Jira Legacy
serverSystem JIRA

(bobswift.atlassian.net)

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

729d679a

8382ec9d-

302c

abb6-

339f

3a29-

958b

8d72-

015e107badcd

95b9a5732a63
keyCACHE-75

The expand settings (expand or contract) are

javascript

JavaScript based and not part of the

html

HTML that is captured by the

cache macro

Cache macro.

cachemacros needing web resources

(warning)


(tick) Confluence 4.x - 5.1

Some compatibility problems on Confluence 5.2 - 5.4.3 due to

Jira Legacy
serverSystem JIRA

(bobswift.atlassian.net)

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

729d679a

8382ec9d-

302c

abb6-

339f

3a29-

958b

8d72-

015e107badcd macro

95b9a5732a63
keyCACHE-63

Resolved with Confluence 5.4.3 and above together with Cache for Confluence 6.3 or above.

Workaround is to put the specific macro somewhere on the page outside of the

cache

Cache macro (this brings in the resources necessary).

If necessary, use the Hide macro with render body to achieve this without showing anything on the page.

cachereport-table(tick)(tick)
Tested with 6.1.
cacheOfficeConnector macros(tick)(tick)Requires release 6.1.


Note

The Cache macro used with the Office Connector macros has a compatibility issue in Confluence version 7.9.0. Refer and watch  

Jira Legacy
serverSystem JIRA
serverId8382ec9d-abb6-3a29-8d72-95b9a5732a63
keyCACHE-346
 for updates.


cacheJIRA macro(tick)(tick)

cachepagetree(warning)(tick)

(tick) Confluence 4.x - 5.1

(tick) Confluence 5.2 or above: Requires Cache for Confluence 6.4 or above

Jira Legacy
serverSystem JIRA
(bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
729d679a
8382ec9d-
302c
abb6-
339f
3a29-
958b
8d72-
015e107badcd
95b9a5732a63
keyCACHE-92
cachepage gadget(warning)(tick)

(tick) Confluence 4.x - 5.1

(tick) Confluence 5.2 or above: Requires Cache for Confluence 6.4 or above

Jira Legacy
serverSystem JIRA
(bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
729d679a
8382ec9d-
302c
abb6-
339f
3a29-
958b
8d72-
015e107badcd
95b9a5732a63
keyCACHE-92
cache

code

code-pro

(warning)(tick)(tick) Confluence 5.2 or above: Requires Cache for Confluence 6.6 or above
Jira Legacy
serverSystem JIRA
(bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
729d679a
8382ec9d-
302c
abb6-
339f
3a29-
958b
8d72-
015e107badcd
95b9a5732a63
keyCACHE-113
cache

excerpt-include

excerpt

(error)
Avoid putting the
excerpt
Excerpt macro within a
cache macro
Cache macro if you need to access the data using excerpt-include.
Jira Legacy
CACHE-183
CACHE-183
cachedetails (Page properties)(tick)



cachedetailssummary (Page properties report)(thumbs down)

Should display properly, but not have any significant performance benefit.

Jira Legacy
CACHE-189
CACHE-189
cacheany asynchronous macro(thumbs down)
Should display properly, but not have any significant performance benefit.
cache

IPython Notebook

  (error)
Indexing of the content is not happening with this app
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId8382ec9d-abb6-3a29-8d72-95b9a5732a63
keyCACHE-278


LegendStatus
(tick)Works
(warning)Works with some restrictions or workarounds
(thumbs down)Is not effective since macro uses asynchronous methods for bringing in data
(error)Does not work in most cases
(question)Unknown