Skip to end of banner
Go to start of banner

Cache macro - Interoperability - 7.x

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Summary

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

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

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 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 another browser.

cache

expand

(tick)(tick)

Reverse the macros — use the Cache macro inside the Expand macro.

Avoid using the Cache refresh parameter. It makes all the Expand macros contract since the 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 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 inside the Expand macro.

Avoid using the Cache refresh parameter. It makes all the Expand macros contract since the Expand macro does not remember the last setting.

Prior to 6.1, workaround is to put an Expand macro somewhere on the page outside of the Cache macro. See CACHE-75 - Getting issue details... STATUS

The expand settings (expand or contract) are JavaScript based and not part of the HTML that is captured by the 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 CACHE-63 - Getting issue details... STATUS

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 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.

The Cache macro used with the Office Connector macros has a compatibility issue in Confluence version 7.9.0. Refer and watch   CACHE-346 - Getting issue details... STATUS  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

CACHE-92 - Getting issue details... STATUS
cachepage gadget(warning)(tick)

(tick) Confluence 4.x - 5.1

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

CACHE-92 - Getting issue details... STATUS
cache

code

code-pro

(warning)(tick)(tick) Confluence 5.2 or above: Requires Cache for Confluence 6.6 or above
CACHE-113 - Getting issue details... STATUS
cache

excerpt-include

excerpt

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



cachedetailssummary (Page properties report)(thumbs down)

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

CACHE-189 - Getting issue details... STATUS
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 CACHE-278 - Getting issue details... STATUS
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


  • No labels