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?
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events