Added:

• We added compatibility with Confluence 7.12.

Fixed:

• The "agreed" disclaimer will be shown in the user's profile in the language the user has agreed to, now.
• Multiple line breaks in the disclaimer will now be shown correctly to the agreeing user.

Added:

• We added compatibility with Confluence 7.12.

Fixed:

• The "agreed" disclaimer will be shown in the user's profile in the language the user has agreed to, now.
• Multiple line breaks in the disclaimer will now be shown correctly to the agreeing user.

For the permanent improvement of our apps we have implemented an anonymous and much reduced app usage. You can find more information here.

For the permanent improvement of our apps we have implemented an anonymous and much reduced app usage. You can find more information here.

We fixed a problem with linked Jira issues when the current disclaimer had not yet been accepted.

We also improved the handling of custom Confluence logos and cleaned up the logging behavior.

We fixed a problem with linked Jira issues when the current disclaimer had not yet been accepted.

We also improved the handling of custom Confluence logos and cleaned up the logging behavior.

We fixed a problem with Oracle databases when configuring Terms of Use.

We fixed a problem with Oracle databases when configuring Terms of Use.

We fixed a problem with PostgreSQL and migration tasks.

We fixed a problem with PostgreSQL and migration tasks.

We're happy to announce Confluence 7 compatibility!

Please note, that this version does not contain any further fixes or features.If you are not using Confluence 7, there is no need to update.

We're happy to announce Confluence 7 compatibility!

Please note, that this version does not contain any further fixes or features.If you are not using Confluence 7, there is no need to update.

Fix for an MySQL issue with the migration from usernames to user keys. The migration task didn't handle deleted users properly. Now it does.

Fix for an MySQL issue with the migration from usernames to user keys. The migration task didn't handle deleted users properly. Now it does.

Features

• We have implemented a WYSIWYG editor, so it's easier for you to create and edit your terms
• Your present terms will be migrated, so there's no loss of data
• For terms with HTML tags, you can still use an HTML editor (not supported by us)
• If you are using Linchpin (or the Linchpin Management Plugin), you can translate your terms into different languages.

Known Issues:

• There can be an exception during upgrade with Postgres due to a bug in Confluence: https://ecosystem.atlassian.net/browse/AO-697. Simply deinstall and reinstall the plugin again to workaround this error.

Features

• We have implemented a WYSIWYG editor, so it's easier for you to create and edit your terms
• Your present terms will be migrated, so there's no loss of data
• For terms with HTML tags, you can still use an HTML editor (not supported by us)
• If you are using Linchpin (or the Linchpin Management Plugin), you can translate your terms into different languages.

Known Issues:

• There can be an exception during upgrade with Postgres due to a bug in Confluence: https://ecosystem.atlassian.net/browse/AO-697. Simply deinstall and reinstall the plugin again to workaround this error.

Ensured compatibility with Secure Login (2FA) and Enterprise Password Policy

Ensured compatibility with Secure Login (2FA) and Enterprise Password Policy

We are happy to announce Data Center and read only mode compatibility

We are happy to announce Data Center and read only mode compatibility

• Technical Cache fixes
• Fix for administration overview of agreements

The PDF uses the styles of the disclaimers html view. Furthermore some special chars are handled correctly.

Desktop vs. PDF view

• You may have designed a clear disclaimer so your PDF should look the same way. This was done in 1.8.

Empty terms should not be displayed

• If you installed the plugin in a version < 1.6 and did not configure any disclaimer, it might happen your users get an disclaimer showing ''undefined'. This disclaimer is not shown anymore in 1.8 and will be deleted once and for all.

The administration section can now always be accessed, even if the disclaimer is not accepted. This enables administrators to deactivate the plugin in case of an error.

Features

• Agreement log for user activities: Administrators are now able to see the user's status regarding the terms, such as "revoked" or "no action yet".
• Version history of previous terms: Administrators can now see the actions users took (or didn't take) to previous terms and review earlier version's of the terms' content.
• Users will see an additional warning so they don't revoke their agreement by mistake.
• Important Confluence actions are always accessible for admins (including 'manage add-ons').

Tasks

• API for Linchpin Mobile: Terms of Use is now available when using the Linchpin Mobile App

Bugfixes

• We have added the context path for accepting and revoking the terms

Features:

• Send a mail to groups and users when a user revokes the terms of use
• All users can now see their own agreed terms of use as tab next to their profile
• It is possible to revoke a previously agreed terms of use

Enhancements:

• Some enhancements to general performance

Bugfixes:

• The terms of use should no longer disappear for unknown reasons

Features

• List of users who accepted the terms of use
• DataCenter readiness

Enhancements

• The app has been technically redesigned

Fixes

• Can't disable terms of use

We removed annoying log messages.

Version 1.3.6 of the Terms of Use plugin fixes a critical bug that could make it impossible to save the disclaimer correctly. This release also cleans up broken database entries.

Features:

• Confluence 5.9 compatibility

Fixes:

• SQL-Statement to be compatible with Oracle Databases
• Endless loop with invalid plugin license

Enhancements

• The Terms of Use site has a CSS body class ("terms-of-use-content"), so you can style it easily

Fixes

• Problems with accepting the Terms of Use caused by case insensitivity side effects in usernames

* improved the SSO support* small bugfixes

A compatible version for Confluence 5.7

* Introducing support for 5.6.1

In this release we added compatibility with Confluence 5.3, 5.4 and 5.5.

All users are required your wikis Terms of Use before being able to logging in and using Confluence.

Features

Before logging the user into Confluence a page with your Terms of Use will be displayed. If the user denies the terms he will be redirected to the login page again. After accepting the user will be normally logged in and his agreement will be stored. He will have to accept the Terms of Use only if the administrator changes the terms.
Administrators can configure a custom title, usage hint and the terms of use itself in Confluence administration console. You can use HTML to format the usage hint and terms of use, like adding headlines, paragraphs, etc. Each time the terms are changed, all users will have to agree again upon login.

Installation

This is a type two plugin, please follow the installation instructions as given by Atlassian: Installation steps via Universal Plugin Manager