com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.
Using Remote Registry Instances for the Registry Partitions
You can configure and use the registry space in one of the following ways:
- Use the registry space shipped by default with the product.
- Use remote registry instances for different registry partitions. These partitions can also be shared across multiple product instances.
This guide explains the second option using WSO2 Governance Registry as the remote registry instance.
The registry space contains three major partitions as local, configuration and governance repositories. Two of these three partitions can be shared across multiple product instances in a typical production environment. Therefore, we can identify four main deployment strategies for the three partitions as follows:
In any of the above four sections, you can mount any WSO2 product to a remote WSO2 Governance Registry instance. Examples discussed here use JDBC-based configuration model as it is the recommended approach for a production setup.
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.