How to replace all hard coded links after a base URL change during a server to server migration

Francois Belair December 5, 2019

We are migrating the content of our confluence server to a new server and the base URL is also changed.

Based on this this reference: https://confluence.atlassian.com/confkb/how-to-replace-all-hard-coded-links-after-a-base-url-change-284366235.html

A simple export with search and replace of the hardcoded link found inside the entities.xml should resolve the problem with broken link.

However, if we try to restore an entities.xml with the updated base URL it will fail without much information in the log.

If we let the current URL stand, the restoration works but the hardcoded links are still referencing to the old server.

The method of search and replace doesn't seem to be in question since we also update other information inside the entities.xml (ie the username that also changed) without any sort of negative impact.

Any reason why a simple change of the base URL would lead to import failure?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events