In this page

Version History
Release Notes
8.1.0
Bye-bye "Archiving Plugin for Confluence"! Hello "Better Content Archiving for Confluence"!
Data privacy (for GDPR)
Upgrading from 8.0.0
8.0.0
Archiving Plugin is a Data Center approved app!
Upgrading from 7.5.0
7.5.0
Upgrading from 7.4.0
7.4.0
Page view initialization
Adding missing page views when updating existing installations to 7.4.0
Multiple supervisors per archiving configuration
Improvements
Upgrading from 7.3.0
7.3.0
Upgrading from 7.2.0
7.2.0
Distinct style for archive spaces
Intelligent label filtering
Improvements
Bugfixes
Upgrading from 7.1.0
7.1.0
Upgrading from 7.0.1
7.0.1
Bugfixes
Upgrading from 7.0.0
7.0.0
Support for Confluence Data Center (cluster)
Sharing data in a cluster
Executing long-running tasks in a cluster
Compatibility with Confluence 6.2
Known issues reported to Atlassian
Upgrading from 6.1.2
6.1.2
Bugfixes
Upgrading from 6.1.1
6.1.1
Bugfixes
Upgrading from 6.1.0
6.1.0
Performance, performance and more performance
Bugfixes
Breadcrumb style page lists removed
Upgrading from 6.0.0
6.0.0
Concept of the Content Update Index
Initializing the Content Update Index
Rebuilding the Content Update Index
Data limiting
Notification email changes
Performance
Bugfixes
Performance tuning guide
Data Center compatibility comes soon!
Upgrading from 5.3.0
5.3.0
Support for Brikit Theme Press 2.0.2
Updated from Bitvoodoo Enterprise Theme 5.1.2
Compatibility tested with Refined Theme 5.1.3 and Scroll Versions 3.3.2
Upgrading from 5.2.0
5.2.0
Differences due to collaborative editing
Bugfixes
Upgrading from 5.1.0
5.1.0
Archiving strategies
Performance improvements in archiving
Upgrading from 5.0.1
5.0.0
Blacklisted spaces
Support for the Scroll Versions Theme and the Bitvoodoo Enterprise Theme
Upgrading from 4.5.0
4.5.0
Customizable notification emails
Automatic archiving on a specific date
Upgrading from 4.4.0
4.4.0
Bulk-apply archiving configurations to spaces
Upgrading from 4.3.1
4.3.0
Page status browser
Page status indicator
"Archive" quick-action in notification emails
Trigger precedence changed
REST API
Upgrading from 4.2.0
4.2.0
Confluence 5.7 compatibility
Upgrading from 4.1.2
4.1.0
New trigger: Archive page if not viewed in last N days
"Pages not viewed recently" list displayed instantly
Space and page archiving is more robust
No email noise
Many-many smaller improvements
Upgrading from 4.0.2
4.0.0
New configure archiving interface
Supervisors
Selectable archiver user
Upgrading from 3.5.0
3.5.0
Confluence 5.5 compatibility
Upgrading from 3.4.0
3.4.0
Page view tracking fixed for large spaces under MS SQL
Upgrading from 3.3.0
3.3.0
Page expiration on a specific date
Upgrading from 3.2.2
3.2.0
Update for RefinedWiki Original Theme
Upgrading from 3.1.0
3.1.0
Confluence 5.3 compatibility
Upgrading from 3.0.0
3.0.0
Page view tracking
Upgrading from 2.3.0
Older releases

Version History

VersionDateNotes
8.1.028/09/2018Data privacy (for GDPR).Release Notes & Upgrade GuideDownload for Server / Download for Data Center
8.0.031/08/2018Support for the new Data Center Approved Apps program.Release Notes & Upgrade GuideDownload for Server / Download for Data Center
7.5.027/06/2018Compatibility release for Confluence 6.10.Release Notes & Upgrade GuideDownload
7.4.006/02/2018Page view initialization. Multiple supervisors.Release Notes & Upgrade GuideDownload
7.3.031/01/2018Compatibility release for Confluence 6.7.Release Notes & Upgrade GuideDownload
7.2.016/10/2017Distinct style for archive spaces. Intelligent label filtering. Various useful improvements.Release Notes & Upgrade GuideDownload
7.1.009/09/2017Compatibility release for Confluence 6.4.Release Notes & Upgrade GuideDownload
7.0.129/05/2017Maintenance release ("Data integrity error in migrated archiving configuration")Release Notes & Upgrade GuideDownload
7.0.024/05/2017Support for Confluence Data Center. Compatibility release for Confluence 6.2.Release Notes & Upgrade GuideDownload
6.1.212/04/2017Maintenance release ("Page Status Indicator overlay is zoomed in" fixed!).Release Notes & Upgrade GuideDownload
6.1.127/03/2017Maintenance release ("Comparison method violates its general contract" fixed!).Release Notes & Upgrade GuideDownload
6.1.030/01/2017Configurable data limits, various bugfixes.Release Notes & Upgrade GuideDownload
6.0.020/12/2016Rebuilt for scalability: Content Update Index and data limiting.Release Notes & Upgrade GuideDownload
5.3.030/11/2016Support for Brikit Theme Press. Updated for Bitvoodoo Enterprise Theme. Re-tested with Refined Theme and Scroll Versions.Release Notes & Upgrade GuideDownload
5.2.014/11/2016Confluence 6 compatibility plus minor bugfixes.Release Notes & Upgrade GuideDownload
5.1.018/03/2016New archiving strategies: Move / Copy and Trash / Trash. Faster archiving.Release Notes & Upgrade GuideDownload
5.0.005/01/2016Blacklists, support for the Scroll Versions & the Bitvoodoo Enterprise themes.Release Notes & Upgrade GuideDownload
4.5.029/09/2015Customizable notification emails, automatic page archiving on a specific date.Release Notes & Upgrade GuideDownload
4.4.020/07/2015Bulk-apply global configurations to spaces.Release Notes & Upgrade GuideDownload
4.3.005/05/2015Real-time page status browser / indicator, "archive" quick-action, REST API.Release Notes & Upgrade GuideDownload
4.2.006/02/2015Compatibility release for Confluence 5.7.Release Notes & Upgrade GuideDownload
4.1.003/11/2014Improved page view tracking, more robust archiving, no email noise.Release Notes & Upgrade GuideDownload
4.0.011/07/2014New "Configure Archiving" interface, support for supervisors and archiver users.Release Notes & Upgrade GuideDownload
3.5.003/06/2014Compatibility release for Confluence 5.5.Release Notes & Upgrade GuideDownload
3.4.008/04/2014Page view tracking fixed for large spaces under MS SQL.Release Notes & Upgrade GuideDownload
3.3.029/01/2014Pages expiring on a specific date.Release Notes & Upgrade GuideDownload
3.2.007/11/2013Update for RefinedWiki Original Theme.Release Notes & Upgrade GuideDownload
3.1.022/10/2013Compatibility release for Confluence 5.3.Release Notes & Upgrade GuideDownload
3.0.023/09/2013New feature: find the Confluence pages not viewed by anyone in the last N days.Release Notes & Upgrade GuideDownload

Release Notes

8.1.0

This release comes with a super-popular feature request implemented to protect personal information. Thanks to Enrico, Florian, Ganna, Karl, Katharina, Michael, Niko, Ralf for helping us with detailing their requirements!

Plus, most visibly, the app got a new name!

Bye-bye "Archiving Plugin for Confluence"! Hello "Better Content Archiving for Confluence"!

With this version we made a slight adjustment in the app's name, because the term "plugin" was replaced by Atlassian first with "add-on" and then with "app". We decided to completely remove this from the app's name.

You may still see the old name popping up here and there, until we roll out the change everywhere. Thanks for the patience!

Data privacy (for GDPR)

From this version, you can configure the visibility of the username of the last updater and last viewer. This feature was primarily requested by users in the EU region in order to protect personal information and comply with GDPR. We suggest reading our FAQ about data protection and GDPR in general.

This screenshot shows the configuration with the last viewer's identity hidden, but with the last updater shown:

It applies to all relevant screens in the Better Content Archiving app:

Learn more about configuring data privacy.

Upgrading from 8.0.0

Just update your app using UPM (the app manager built in to Confluence).

8.0.0

As you probably know, Archiving Plugin already supports Confluence Data Center deployments (i.e. clustered Confluence). To be precise, those are supported since app version 7.0.0 (released in May 2017).

In 2018, Atlassian re-launched its Data Center program and introduced new development and testing criteria for "Data Center approved apps". This version is the official release for the revised program, tested to live up to the rigorous demands of Data Center environments.

Archiving Plugin is a Data Center approved app!

The followings have been done to comply with the revised development and testing requirements:

  1. This version has been verified against the Atlassian's official Data Center technical checklist, which would identify potential non-cluster-safe parts in the app. All points are met.
  2. This version has been performance-tested with the official Atlassian Performance Testing Library. For your interest, we used AWS infrastructure and "c3.xlarge" type standard EC2 instances for hosting the Confluence nodes. The testing confirmed that the app works correctly and consistently in clusters with 1, 2, 4 and 8 nodes (and anything in-between).
  3. This version has been successfully tested with UPM 3.0, the new generation of the Universal Plugin Manager.

As a result, Archiving Plugin is a Data Center approved apps launch partner. The new program was announced at Atlassian Summit 2018 (3-5 September 2018, Barcelona).

Upgrading from 7.5.0

Just update your app using UPM (the app manager built in to Confluence).

7.5.0

This version is a compatibility release for Confluence 6.10.

Upgrading from 7.4.0

Just update your app using UPM (the app manager built in to Confluence).

7.4.0

Page view initialization

As you probably know, Confluence does not implement any sort of page view tracking. Because the workflows implemented by Archiving Plugin heavily rely on the last page view information, the app implements its own real-time page view tracking mechanism. Even with this mechanism in place, there was a limitation that confused many in the past. We call it the "abandoned pages" problem.

This version introduces a new feature to solve this problem. While this is still impossible to find out what happened before the app's installation (building a time machine is really hard! :-)), you can sensibly initialize the last page view information when building or re-building the content event index!

You can use the strategies that fits your users' expectations the best:

Learn more about page view initialization.

Adding missing page views when updating existing installations to 7.4.0

After updating the app version, we encourage you to re-build your global Content Event Index and add the last page view information for the pages without that. You can use one of the following strategies:

  1. Using the "the same as its last update" strategy: it sets the last view for abandoned pages the same as their last update. Please expect the consequences detailed in the next paragraph.
  2. Using the "its last updater and a specific date" option with the current date: it sets the last view to today. It is the safest option with no immediate consequences. If the abandoned pages are continue to stay non-viewed, they will be reported after the page view alert interval.
  3. Using the "its last updater and a specific date" option with a past date: by setting the last view to some user-given date it finds the abandoned pages faster. Please expect the consequences detailed in the next paragraph.

After you initialized the page view for abandoned pages (i.e. when all page has valid last view information), the app will start processing the pages it skipped previously. You can expect the following consequences:

  1. The "not-viewed pages" counts in Content Quality Statistics may increase (with the count of the abadoned pages added).
  2. The "not-viewed pages" lists in notification emails may be longer (with the abandoned pages added).
  3. Most importantly: if you are using the "not viewed for N days" trigger for page archiving, it may trigger archiving for abandoned pages!

If you are worried about these, try the page view initialization feature in a staging system (that has a copy of your production data) first.

Overall, as these abandoned pages will now be precisely tracked and reported, you can take actions to make your content leaner and its quality even better.

Multiple supervisors per archiving configuration

Starting from this version, you can select multiple users as supervisors in any archiving configuration. (In previous versions, you could select only one.) This allows making more than one person responsible for the space, resulting in even better content quality.

Improvements
  • Content Quality Statistics and Start Archiving screens give a clear error message when long-running tasks cannot be started due to missing actors (i.e. when the "confluence-administrator" groups that contains the super-user does not exist or does not contain at least one valid user account).
  • Archiving configuration editor gives more intuitive validation messages (related to the page view- and update intervals for various triggers).
  • User interface improvements: the term "actor" is more consistently used, the "archive space's status" selector is more intuitively explained.
  • Content improvements on the built-in Getting Started page.
Upgrading from 7.3.0

Just update your app using UPM (the app manager built in to Confluence). As a second step, add the missing page view information for the pages without that.

7.3.0

This version is a compatibility release for Confluence 6.7.

Upgrading from 7.2.0

Just update your app using UPM (the app manager built in to Confluence).

7.2.0

Distinct style for archive spaces

One of the user feedback we received time to time was that users unwantedly edited archive pages because they didn't realize that they are in an archive space's context. To address this, the app gives a clear, but non-obtrusive style to archive pages from this release. It includes a yellowish background color plus an expressive watermark. It is visible both on the wiki pages and in the space's administration screens to discourage "update" type operations.

Intelligent label filtering

Labels are used for various mechanisms in Confluence. From this version, when a page is moved or copied to the archive space, its labels are filtered to avoid unexpected behaviour.

Improvements
  • Notification email templates have access to the archiving configuration to enable more informative notifications
    • "Not-viewed pages" emails display the "page view alert limit"
    • "Expired pages" emails display the "page expiration alert limit"
  • The Customizing notification emails page in the documentation was rewritten for clarity and with more examples
Bugfixes
  • Fixed: Inline comments become regular page comments in the archive space
  • Fixed: Favorite pages are listed twice in the favorites list (once from the fresh space and once from the archive space)
  • Fixed: Page renaming unexpectedly updates the last update date of the linked pages (by intercepting the events triggered by "LINK_REFACTORING")
  • Fixed: Incomplete page and attachment data causes "Cannot set non-null field UPDATE_DATE to null" error while re-building the content update index
Upgrading from 7.1.0

Just update your app using UPM (the app manager built in to Confluence).

7.1.0

This version is a compatibility release for Confluence 6.4.

Upgrading from 7.0.1

Just update your app using UPM (the app manager built in to Confluence).

7.0.1

Bugfixes
  • Fixed: "Data integrity error in migrated archiving configuration" error when upgrading to app version 7.0.0
Upgrading from 7.0.0

Just update your app using UPM (the app manager built in to Confluence).

7.0.0

Support for Confluence Data Center (cluster)

We are happy to announce that this app version implements the long awaited support for Confluence Data Center deployments!

Over the last 10 months we put insane efforts to the 6.x releases (the grounding work) and to this new release, aiming to provide Content Lifecycle Management for Confluence clusters. 6.x allows to efficiently process millions of pages, while 7.x allows to do that over multiple Confluence nodes.

The video below gives a short introduction to running the app on a cluster of 3 Confluence nodes. We first start the Calculate Quality Statistics task on node 1, then demonstrate that its progress can also be watched on node 2 and node 3. At completion, the result becomes visible on all nodes with no latency. Overall, the user experience is 99% identical with the single-server user experience!

Without going much into technical details, here is some high level information about how Archiving Plugin works in a cluster.

Sharing data in a cluster

All persistent Archiving Plugin data is managed using the ActiveObjects technology (by Atlassian). It guarantees that all database-persisted data and all changes are transparently replicated among the cluster nodes. Archiving configurations are an example of database-persisted data.

For non-persistent data that need to be shared among cluster nodes, Archiving Plugin uses cluster-wide caches relying on the Cache 2 technology (by Atlassian). It guarantees that all cached data are replicated among the cluster-nodes in nearly real-time. Long-running task state (progress) is an example of non-persistent data.

Executing long-running tasks in a cluster

The app's long-running tasks (like the Content Quality Calculation or the Content Archiving task) are executed only on one node in the cluster, generating load only on that single node! At completion, Archiving Plugin makes sure that the task results are replicated to all other nodes. For instance, the refreshed Content Quality Statistics are immediately visible on all nodes.

The task parallelization strategy is simple: at any time, there can be max one task being executed in the whole cluster. In other words, there is simply no parallelization. When a node wants to execute a task, it needs to acquire a cluster-wide lock and then release that at completion. Until that lock is available again, no other task can be started on any other node. The idea is to save the cluster from synchronization issues and from unnecessary load. As long-running tasks complete fast since the 6.0.x versions of the app, this simple and robust strategy will not be a limiting factor for through-put.

While the actual task is executed on a single node, other nodes allow tracking its progress using so-called proxy tasks. A proxy task on its own node appears like the actual task running on another node, displaying the message, the progress and the result of that. From the user point of view, proxy tasks make transparent whether the task is actually running on the node the user is connected to or on some other node.

All in all, the new era of highly-available Content Lifecycle Management has started. Happy clustering!

Compatibility with Confluence 6.2

This version is also a compatibility release for Confluence 6.2.

Known issues reported to Atlassian

There are two pending issues at the time of the release, that we reported for Atlassian. These are affecting the Archiving Plugin in some negative way, but cannot be fixed in the app side (at least the probability that these can be improved in our side are low).

Therefore we encourage you to step in, vote for these issues, add your details as a comment and watch the issue for potential updates. (Our hope is that the increased importance leads for faster results from Atlassian.)

  1. Mysterious "no row with the given identifier exists" errors when moving pages: CE-1044
  2. Page moves are significantly slower (although stable!) in newer Confluence versions than in Confluence 5.7: CE-1045
Upgrading from 6.1.2

Just update your app using UPM (the app manager built in to Confluence). Please note that after the upgrade you will have to recalculate the content quality statistics, because from this version those are now stored in a new "cluster-ready" database table.

6.1.2

Bugfixes
  • Fixed: Page Status Indicator is displaying an error for previous page versions
  • Fixed: The content of the Page Status Indicator overlay is "zoomed in" when the Comala Workflows app is installed
Upgrading from 6.1.1

Just update your app using UPM (the app manager built in to Confluence).

6.1.1

Bugfixes
  • Fixed: "Comparison method violates its general contract" errors in Confluence core when Archiving Plugin screens are accessed (reported to Atlassian as CONF-45910)
  • Fixed: Page edits with "Notify watchers" unchecked (also known as "minor edits") do not refresh the page's Last Update date
Upgrading from 6.1.0

Just update your app using UPM (the app manager built in to Confluence).

6.1.0

Performance, performance and more performance

In the previous app version (6.0.0), we introduced the so-called data limits to save your server from wasting computing resources (CPU, memory) on irrelevant data. In this version, we rebuilt the end of the data processing pipeline for even more performance and lower memory footprint. This enabled to significantly increase the defaults of the data limits, which are configurable now!

Data limit parameterDefault value
events.maxSpaces1000
events.maxPagesPerSpace200
notifications.maxSpaces1000
notifications.maxPagesPerSpace100000
emails.maxSpaces200
emails.maxPagesPerSpace100

Using these data limits, several thousand notification emails (for hundreds of spaces and several hundred thousand pages) were sent without problems in our internal load tests:

Bugfixes
  • Fixed: Hibernate "owning Session was closed" error while collecting the addressees for notification emails.
  • Fixed: Empty page lists in archiving events cause NPEs with Oracle.
  • Fixed: Blacklist checking crashes on the spaces that have no description object associated with (i.e. their data is corrupt).
  • Fixed: When all spaces are blacklisted, the Content Quality Stats screen misleadingly suggests that the system is in an unindexed state.
Breadcrumb style page lists removed

Breadcrumbs-style page lists in the notification emails are not supported anymore. You can't displays the ancestors of an expired page, like "grandparent > parent > actual page", only display the actual page. We did for two reasons. First: that's not the Confluence standard. Second: carrying all ancestors with the pages until the mail rendering logic generated extra complication (ancestors are lazy loaded Hibernate objects) and extra use of memory (ancestors are heavy weight), so we're keeping things simple, robust and scalable.

Upgrading from 6.0.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

6.0.0

This release introduces the next-generation app core, that was rebuilt from bottom to top, with scalability in mind.

More than 8 years ago, when we released the first version, we didn't expect the app to grow this popular. Today it improves the content quality for more than 500 production Confluence instances, from small instances to extremely large ones. When we say "extremely large", we mean Confluence instances with more than 1.5 million pages, containing individual spaces with more than 100,000 pages! (These are real-life examples we received from our largest customers.)

With proper tuning, previous app versions gave acceptable results even on this scale of data, but clearly there was room for improvement.

6.0.0 is our answer for scalability. (We put in countless weeks working on 6.0.0, and this is our biggest release since the inception.)

Apart from re-architecting many components under the hood and from a ton of smaller visible improvements, the app features work identically in pre-6.0.0 versions and 6.0.0. The latter will be, however, significantly faster in large Confluence instances:

  • background tasks are completed in minutes instead of hours
  • as background tasks are faster, you can execute them more frequently, therefore your statistics are more up-to-date
  • memory requirements are lower
  • database transactions are fewer and shorter

These changes allow scaling even to the magnitude of millions of pages!

Concept of the Content Update Index

The introduction of the Content Update Index is the single most important change in this release. Without going into details, the index maintains the last update information (who updated what, when?) in a scalable and searchable way, eliminating expensive page tree traversals.

Although the index does not require any manual care, you need to initialize that the first time, and may need to rebuild that eventually on the go.

Initializing the Content Update Index

The index must be initialized when the app is installed the first time, or when you upgrade to version 6.0.0. Until the content update index is built, the app functionality that relies on content updates will not work, for obvious reasons.

The initialization must be executed globally by a Confluence administrator:

  1. Login to Confluence as administrator
  2. Go to AdministrationContent Quality
  3. Click the Build now button

After the index is initialized, it will be automatically maintained in the background with "micro updates" that are triggered by page updates, attachment updates, and so.

Rebuilding the Content Update Index

In some rare cases, you may want to rebuild the index. This can typically happen when you remove spaces from the blacklist (the index is not maintained for blacklisted spaces), or when you are experiencing troubles with the app features (potentially caused by index inconsistency).

You can rebuild the index both globally or for a single space, by clicking the Re-build content update index button in the Content Quality Statistics screen.

Data limiting

Starting from this release the app reduces the data to the "actionable" size. It both prevents your users from information overload and your system from wasting resources on useless work.

If, for example, you had 100,000 expired pages in 500 spaces, then your users may have received gigantic notification emails with super-long page lists previously. Not only those were unreadable, people just ignored them, due to the "where do I start fixing this?" problem.

In 6.0.0, although all the 500 spaces and 100,000 pages are processed, it will intelligently limit the notification emails to the first 20 spaces and to the first 20 pages per space, making it more actionable for the user. A similar mechanism is in place to guarantee that only 50 pages are stored per archiving event.

Notification email changes

Along with other mechanism in the app, notification emails were re-engineered with large dataset in mind. Notable changes:

  • Both the list of spaces and the list of pages per space are limited to the first N items.
    Previous app versions displayed the complete lists, which is not actionable (will you really update a list with a thousand expired pages?) and may result in multi-megabyte long emails (that may even break some email clients).
    The new approach is more manageable for the users and scales better for large amount of content.
  • Page lists are sorted alpahbetically, not "by page tree".
    Previous app versions used complete space traversals to reconstruct the page tree for the emails. This was slow and did not scale well to large spaces.
  • Breadcrumbs are turned off.
    In previous app versions, pages were displayed with the whole trail of their parent pages in the emails, like "Home Page → Finance Report → 2015 → Q1 → Sales". For a shorter list of pages, especially if they were organized into a logical page tree, it was great. For a longer list of pages, it made the list harder to read, plus it does not follow the convention how the Confluence interface displays page lists in general.
    Therefore we decided to turn this off for a better default setting, but you can turn this on by setting this variable to true in each email template:
    ## expired-pages-notification.vm
    #set($showParentPages = false)  ## whether to display the parents, grandparents, etc. of each page
    
Performance

Performance in this case is a function of several different parameters (and your mileage may vary!), but let us give you some rough results from our load testing environment. Please note that the environment we chose is relatively modern and powerful, but this is deliberately not a high-end server. Our goal was to stay close to or even "below" reality.

Our environment:

  • "Hardware": m4.large instance on AWS EC2 (2 CPU, 8G RAM, SSD storage)
  • Operating system: Linux (Ubuntu Server 14.04)
  • Confluence versions: 5.7 and 5.10
  • Database: MySQL 5.6
  • JVM tuning: we were only experimenting with heap sizes 1000M, 1500M and 3000M, all other JVM settings are Confluence defaults

Our results: (you can get different numbers in your environment!)

Operation 1.014M pages in Confluence 5.7.6 380K pages in Confluence 5.10.1
Content update indexing 25 mins 7 mins
Content quality recalculation 1 hour 6 mins
Page view tracking 16 minutes (for 175K not viewed pages) 5:30 minutes (for 160K not viewed pages)
Page expiration tracking 25:30 minutes (for 453K expired pages) 8:20 minutes (for 380K expired pages)
Page archiving with MOVE 40 minutes (for 1555 pages) 1.1 hours (for 400 pages - stable, but slower!)
Page archiving with COPY 53 minutes (for 1555 pages) 1.5 hours (for 1601 pages)
Page archiving with TRASH 1 minute (for 1555 pages) 35 seconds (for 2801 pages)
Bugfixes
  • In previous versions, no pages found to archive if the archiving configuration specified the "AND" operator between the Page Archiving triggers "Not viewed for N days" and "Not updated for M days", and one of those were disabled.
    This was a major bug (reported by a user in Italy, thanks!) with a simple workaround: turn the operator to "OR" and it will work as expected. Ultimately, 6.0.0 fixes this.
  • The Content ToolsPage Status is now hidden for regular users.
    It was previously shown, but required space administration permissions to access. Note: we consider making this accessible by regular users in a future app version, but for now we just made the UI less misleading.
  • Manage blacklisted spaces link is only displayed for Confluence administrators even in space context.
Performance tuning guide

Our new performance tuning guide gives you simple to execute instructions to run the app efficiently even in super-large environments.

Data Center compatibility comes soon!

This is important to note that 6.0.0 is also the "groundwork release" for Data Center compatibility. Confluence Data Center support is our most popular feature request at the moment, which requires many of the changes introduced by this new app core, therefore 6.0.0 is a sort of prerequisite for that.

Upgrading from 5.3.0

Steps:

  1. Upgrade the app JAR as usual, through the Universal Plugin Manager.
  2. Then reset each notification emails to the factory default, due to the email template changes mentioned above.

Upgrading to this version is recommended if your Confluence is larger than 30 spaces and 1500 pages.

5.3.0

This version focuses on improving the integration with various space themes. By introducing the Brikit Theme Press support, Archiving Plugin now supports all major Confluence themes, including built-in types and the types provided by 3rd party apps.

Support for Brikit Theme Press 2.0.2

Starting from this version, you can use the Archiving Plugin also in the spaces relying on the popular Brikit Theme Press app.

Updated from Bitvoodoo Enterprise Theme 5.1.2

We updated this integration to the latest Enterprise Theme app version:

  1. Fixed: Page Status Indicator is not visible
  2. Fixed: "Archiving" tab in Space Tools is duplicated
Compatibility tested with Refined Theme 5.1.3 and Scroll Versions 3.3.2

We also verified the Archiving Plugin working correctly with these two popular theme apps. (OK, Scroll Versions is not a theme app by design, but this also introduces its own theme.)

Upgrading from 5.2.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

5.2.0

This version is a compatibility release for Confluence 6 with additional minor bugfixes.

Differences due to collaborative editing

Confluence 6 introduced collaborative editing. The only difference it means for the Archiving Plugin is that any "partial page update" will update the last update timestamp of the edited page. In other words, when any of the users editing the same page at the same time saves his/her "partial" changes, that will make the page current. From that point, everything works just as in previous app versions.

Bugfixes
  • Fixed: Page titles in page lists (like "expired pages") overlap with the page icons
  • Fixed: When archiving page comments, certain "mentions" result in unwanted mail notifications
  • Fixed: "Archiving" and "Archiving configuration" tabs are displayed in archive spaces
Upgrading from 5.1.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

5.1.0

Archiving strategies

Starting from this release, there are 3 ways to archive pages:

  1. Move them to an archive space ("Move" strategy),
  2. Copy them to an archive space and delete them in the fresh space ("Copy and Trash" strategy)
  3. Or just delete them in their original space ("Trash" strategy)

Each of these have their own merits, but "Move" is the new default, as it fits the most use cases the best.

"Move" implements the most requested feature to preserve the full version history for archived pages. Thanks for everyone asking for this, we appreciate your patience and your help in finding the perfect roadmap for the app! Keep it comin'!

After upgrading to this version, consider switching existing archiving configurations to "Move" (guide).

Performance improvements in archiving

The archiving logic used in previous app versions is now called "Copy and Trash". Even this strategy is faster than it was before, but "Move" is faster in most circumstances and "Trash" is blazingly fast.

Upgrading from 5.0.1

Just update your app using UPM (the app manager built in to Confluence), that's all.

5.0.0

Blacklisted spaces

Turn off the Archiving Plugin for those spaces that are not relevant or have corrupt data, to improve the app performance and stability.

Support for the Scroll Versions Theme and the Bitvoodoo Enterprise Theme

This release adds official support for two highly popular 3rd party space themes.

Upgrading from 4.5.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.5.0

Customizable notification emails

The content of all 4 notification emails types (non-viewed pages, expired pages, archived pages, skipped pages) are editable via a web based editor. In previous versions, you could edit the templates by exploding the app JAR, but localization, adding your own content is now super easy.

Automatic archiving on a specific date

Just add the label "archive-15/12/1" and the page (plus its descendants) will be automatically archived on 1 Dec 2015. It couldn't be more fire-and-forget. Use it carefully, and make sure you don't shoot yourself in the foot.

Upgrading from 4.4.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.4.0

Bulk-apply archiving configurations to spaces

A new screen, available using the "Spaces" link from the "Global Configurations" screen, allows quickly applying a global configuration to multiple spaces in one go. This is a huge time saver if you have a large number of spaces.

(This was the most popular feature request at the time. We take your feedback seriously, thanks!)

This release also features some bugfixes, most importantly a fix for an infamous Java 7/8 incompatibility problem.

Upgrading from 4.3.1

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.3.0

Page status browser

Conveniently browse through the pages in a space, with their real-time status, last update dates, last view dates displayed.

Page status indicator

Page status is also shown in the top-left corner of the content pane.

"Archive" quick-action in notification emails

Adding the "archive this page" label is now available in the notification emails! While looking at the list of expired pages, you can update or archive them with a single click.

Trigger precedence changed

The evaluation order of the archiving sub-triggers is now more intuitive. Recommendation: review your archiving configurations that use all the 3 sub-triggers!

REST API

Although the primary aim of the new API is to provide back-end for the app's own user-interface, you are also welcome to use it for your reporting and integration purposes.

Upgrading from 4.2.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.2.0

Confluence 5.7 compatibility

This is primarily a compatibility release with no major changes in features.

Upgrading from 4.1.2

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.1.0

New trigger: Archive page if not viewed in last N days

You can flexibly combine this new trigger with others, like "and if it has not been updated in the last Z days or has been labelled with 'archive'".

"Pages not viewed recently" list displayed instantly

The count of "pages not viewed recently" is now displayed in the Content Quality Statistics table, and it contributes to the overall quality metric. Click that link to view the exact page list.

Space and page archiving is more robust

The rewritten code is more fault tolerant and handles concurrency better.

No email noise

No unwanted notification emails are sent at page archiving (creations, deletions), comments, attachment or mentions.

Many-many smaller improvements

Numerous fixes and changes were made on the UI (ex: convenience links, hiding the archiving functionality for archive spaces), on Internet Explorer compatibility (ex: non-clickable buttons) or in the internals (ex: improved logging).

Upgrading from 4.0.2

Just update your app using UPM (the app manager built in to Confluence), that's all.

4.0.0

New configure archiving interface

In 4.0.0, the new configuration experience is based around the concept of triggers ("if a page is older than 10 days" or "if a page labelled with 'foo'"...) and actions (...then "notify its last modifier"), allowing fine-grained settings and eliminating confusion. The rules of "who receives what email" are 100% configurable.

Supervisors

To send notifications to users that are not "directly" related to the content (not authors, etc.), configure so-called supervisors. To route all notifications to a single external mailbox, just set up a Confluence user with that email address and select that as supervisor.

Selectable archiver user

Previously, archiving operations (like copying and deleting pages) were executed by a user account automatically selected by the app. It lead to some misunderstanding.

The archiver user can now be manually picked. Tip: set up an intuitively named user account (ex: "Wiki Archiver") for that.

...oh, did you see our new docs?

Upgrading from 3.5.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.5.0

Confluence 5.5 compatibility

This release is updated for the Confluence 5.5 line. In addition, some minor internal glitches were also fixed.

Upgrading from 3.4.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.4.0

Page view tracking fixed for large spaces under MS SQL

This version is a maintenance release, that fixes a problem with the "page view tracking" feature, when used with MS SQL on very large spaces.

Upgrading from 3.3.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.3.0

Page expiration on a specific date

To satisfy the most popular feature request, page expiration is now also checked against specific dates, not only against periods starting from the last update.

Just add the tag "expire-14/2/25" and you will be notified when the page expires on 25 February 2014. It is supported for single pages and page tree as well, and integrates seamlessly with the other features (statistics, event streams, notifications).

Upgrading from 3.2.2

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.2.0

Update for RefinedWiki Original Theme

Archiving Plugin now also supports the slightly modified Space Administration interface introduced by RefinedWiki Original Theme, one of the most popular custom theme apps for Confluence.

Upgrading from 3.1.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.1.0

Confluence 5.3 compatibility

This release is updated for the Confluence 5.3 line.

Upgrading from 3.0.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

3.0.0

Page view tracking

This app version introduces a new feature called page view tracking to find those Confluence pages that were not viewed by anybody for a period of time. Discover both outdated (not edited by anyone) and irrelevant (not viewed by anyone) wiki content. Archive that easily to prevent efficiency, productivity and consistency problems.

Upgrading from 2.3.0

Just update your app using UPM (the app manager built in to Confluence), that's all.

Older releases

Regarding older releases please contact us. We are happy to provide you both with the apps and the corresponding upgrade instructions.