Confluence 7.19 Upgrade Notes
Here are some important notes on upgrading to Confluence 7.19. For details of the new features and improvements in this release, see the Confluence 7.19 Release Notes.
On this page:
Confluence Server and Data Center 7.19 is a Long Term Support release
This means we'll provide bug fix releases until 7.19 reaches end of life, to address critical security, stability, data integrity, and performance issues.
End of support announcements
Advance Notice: End of support for Oracle 12c
Confluence 7.20.x will be the last release to support Oracle 12c.
Advance Notice: End of support for the following databases:
- We will end support for MySQL 5.7 in Confluence 8.0.
- We will end support for PostgreSQL 11 in Confluence 8.0.
- We will end support for H2 embedded database in Confluence 8.0.
Advance Notice: End of support for Java 8
We will end support for running Confluence with Java 8 in Confluence 8.0.
Advance Notice: End of support for UTF8 encoding for MySQL
We will end support for UTF8 encoding for MySQL databases in Confluence 8.0. If you run Confluence with a MySQL database, you should use UTF8MB4 encoding.
Advance Notice: Removal of Usage stats
We will remove the Usage Stats feature in Confluence 8.0.
For more information on these notices, see End of Support Announcements for Confluence.
Head to Preparing for Confluence 7.19 to find out more about changes under the hood.
- There is a known issue where the Task Report macro returns a timeout or error state when faster permissions is enabled. As a temporary fix, we will not use faster permissions on this macro in Confluence 7.19.2 and later.
- There is a known issue where upgrading Confluence on Microsoft SQL Server fails with an 'invalid column name' error. See CONFSERVER-66547 for a workaround.
- There are a number of known issues when upgrading Confluence on specific database versions. See Confluence 7.11 upgrade notes if you are upgrading from Confluence 7.10 or earlier.
- There's a known issue running PostgreSQL on Azure with the bundled version of the driver (42.2.16). See CONFSERVER-60515 for a workaround
- If you are upgrading from Confluence 6.3 or earlier, there's a known issue where spaces do not appear in the space directory. You'll need to reindex your site after upgrading to fix this.
- If you use Apache to limit who can access the admin console, you should update your configuration. See Using Apache to limit access to the Confluence administration interface for our suggested configuration.
- There is a known issue where read-only mode attempts to write to
<shared-home>/confluence.cfg.xml, but the file doesn't exist in the shared home directory. This problem affects sites that have been previously upgraded from Confluence 6.0 or earlier. See Could not save access.mode into the shared confluence.cfg.xml file error after upgrading to Confluence Data Center 6.10
- There is a known issue where some fonts that Confluence relies on are not available in older Linux distributions. See Confluence UI shows garbled or corrupt text on CAPTCHA, macros, and/or diagrams due to missing fonts
If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.
Always test the upgrade in a test environment before upgrading in production.
To upgrade Confluence to the latest version:
- Go to > Plan your upgrade and select the version you want to upgrade to. This will run the > General Configurationpre-upgrade checks.
- Go to > Troubleshooting and support tools > General Configuration to check your license validity, application server, database setup and more.
- If your version of Confluence is more than one version behind, read the for all releases between your version and the latest version.
- Back up your installation directory, home directory and database.
- Download the latest version of Confluence.
- Follow the instructions in the Upgrade Guide.
Update configuration files after upgrading
The contents of configuration files such as
server.xml, web.xml ,
confluence-init.properties change from time to time.
When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation, otherwise you will miss out on any improvements we have made.