Cache for Confluence Release 5.1

2012-11-29






Highlights

Performance improvement

An id parameter can (optionally) be specified to uniquely identify a cache macro on a page. If specified, this can improve performance when doing previews and macro browser previews by reducing the number of cache refreshes needed. An explicit id means that a single cache entry can be used as you move between view, full edit preview, and macro browser preview. Of course, if you make an actual change in the macro browser, the cache will need to be refreshed, but normally only once in the cycle between macro browser refresh, preview, and actual showing the page.

Other improvements and fixes

  1. Split refresh date from body text - this fixed a regression from previous behavior
  2. Support install on Confluence 5.x for the EAP
  3. Better error handling on browser preview

Resolved issues

type key summary reporter assignee priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Find answers from the community.

Ask a question to the community.

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.