Broken Anchors & Tags on Document Move
Asked by Ivor Matz:

Since using the new editor, when I move a document from one portal (staging/review) to another portal (approved/active) ++*ALL*++ the internal tags (e.g., #AppendixA) that link to an anchor (e.g., Appendix A) simply disappear and I have to reset them. Some of the hot-links to other documents, but not all, also disappear. It happens every time and only started happening when the new editor was installed.

I really don't like the new editor anyway. It's much more limited and klunky than the earlier editor and I'm not really sure why it needed a radical revision. I'd like to know how to return to the earlier editor and lock-out the newer version so I never have to work around it again.

Thanks!


Answers:
author: Diego
body: Hello [@Ivor Matz](/t5/user/viewprofilepage/user-id/2984457) !

As I understand, your workflow depends on the migration of content created within a review Confluence site into the production Confluence site. After the migration to the New Editor (Fabric), this workflow has been somewhat broken.

If the description above matches what you are experiencing, I would like to ask you a few questions. Here we go:
> 1. *Does your Staging/Review Confluence site use the New Editor (Fabric)?*
> 2. *How were the anchors created on the original page (before migrating into the production site)?*
> 3. *Are "hot-links" links that point to attachments?*

++*Anchors have been removed in the new editor and have been replaced by Linkable Headings.*++Here is the description of this feature:
> Heading links use a combination of the three character space identifier and the page ID along with the page name and header name.
>
> If you only need to get the URL that takes viewers to a heading, do the following:
>
> 1. Navigate to the page and scroll down to the heading.
> 2. Hover over the heading to reveal the link icon to the left of the heading.
> 3. Click the link icon to copy the link.
> 4. Navigate to and edit the page where you want to link to the heading.
> 5. Paste the URL in the link tool pop-up, and give it a more friendly name if desired.
>
> If you need to create several links to headings on a page, it's more efficient to get the page URL and construct the heading portion yourself.
>
> 1. Navigate to and view the page containing the heading.
> 2. Copy the page URL for future use. Keep in mind that the page URL capitalization must match the page title capitalization. Spaces in the page title are replaced with a plus ( + ).
> 3. Make note of all the exact headings that to which you want to link.
> 4. Navigate to and edit the page where you want to link to the headings.
> 5. Paste the page URL in the link tool pop-up, add the page heading title, and give it a more friendly name if desired. Keep in mind that the heading part of the URL must match the capitalization of the page heading. Spaces in the heading title are replaced with a hyphen ( - ).
> 6. Repeat Step 6 until you've created all the heading links needed.

If you need more detail on links and their types, you can check here:
> * [++***\[Confluence Cloud\] Insert links and anchors***++](https://support.atlassian.com/confluence-cloud/docs/insert-links-and-anchors/)

The suggestion to add anchors back into the New Editor experience was made some time but was ultimately *ruled out in favor of Linkable Headings*:
> *Hi everyone,*
>
> *Thank you for your feedback on adding page anchors into the new editor. We currently have link to headings that are natively supported in the new editor without the need for the old Anchor Macro. You can directly reference headers by copying the link upon hover or by adding #Header-Name to the URL of your page. With our originally announced plan to clean up macros (<https://confluence.atlassian.com/confcloud/we-re-cleaning-up-our-macros-946028471.html>) and our implementation of link to headings, we currently have no plans in the near term to bring back the Anchor Macro in its original state.*
>
> *You can track our upcoming roadmap here: <https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html>. If we have any updated plans, we will update the thread here. Thank you again for your feedback.*
>
> *Best,*
>
> *Sunny*

Link to report:
> * [++***\[Confluence Cloud\] Add Page Anchors back into the new editor experience.***++](https://jira.atlassian.com/browse/CONFCLOUD-66773)

If my guess is correct, hot-links refer to links that point to attachments. With this definition in mind, I can tell you that this feature is yet to be deployed in our new editor:
> * [++***\[Confluence Cloud\] Ability to link text to an attachment in editor***++](https://jira.atlassian.com/browse/CONFCLOUD-65302)

The current status is listed as **In Progress**. Which means we are already working on it.

If your workflow currently depends heavily on features that are not yet present or deprecated in our new editor, I believe that the following blog post may be helpful:
> * [++***\[Atlassian Community\] Change to your content is in your hands***++](https://community.atlassian.com/t5/Confluence-Cloud-articles/Change-to-your-content-is-in-your-hands/ba-p/1324476)

However, I would weight whether or not the Legacy Editor should be kept around within your production site. Mostly because of these reasons:
> 1. There are no improvement efforts for the Legacy Editor (it is to be used "as is")
> 2. New flows may be introduced and the legacy editor will not be part of it. An example of it is the new creation flow.
> 3. No minor bugs are going to be fixed.

While there is no foreseeable future where we completely remove the Legacy Editor, it will be increasingly out of pace with new features and flows implemented within Confluence itself.

For more insights on what is and what is not available in Confluence. you can check our roadmap:
> * ++***[Confluence Cloud Editor Roadmap](https://support.atlassian.com/confluence-cloud/docs/confluence-cloud-editor-roadmap/)***++

Let us hear from you!


Tags: cloud