We use pages as static material and when we change the content we make a copy of the page, edit the changes, and replace previous page with the new page.
Problem is when the pages have anchors to other pages and the referenced page is similarly "replaced" and the anchor follows the old/previous page.
How do we either stop that behavior OR properly use anchors so they'll consistently point to the original page name - in our case it's "Glossary"?
looks like you need some kind of publishing mechanism for your spaces.
We are using a plugin for that: Comala Publishing
With this plugin you are able to create a "draft space" as a copy of your public space and then edit your pages in the draft space and publish them to your public space. You don't need to replace pages, there's just a new version of the same page.
Works fine for us and might help you. But it is not for free... And only for self hosted Confluence.
(btw. I am not working for them, just using their plugin, but I like it :-) )
Unfortunately our "publishing" procedure is to have the WIPs separate - the main pages are publicly viewable but the proposed changes needs to be reviewed and approved which is why I do it the other way - copy the current page to a our "stage" which is restricted, changes are made, to it, shared to the people for review, the current/old content is then renamed to a different location (archive which Confluence then updates all of the dependent anchors), and then new page is placed into the normal location for public viewability and thus my problem.
Music, at its essence, is what gives us memories. And the longer a song has existed in our lives, the more memories we have of it - Stevie Wonder This week's Friday Fu...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs