Broken Pages after Bulk Conversion from Legacy editor to New editor

XMLWordPrintable

    • 8
    • Severity 3 - Minor
    • 1

      Issue Summary

      Some pages are broken after Bulk Conversion from legacy editor to the new editor.

      After the conversion happens, the page will present the below error message:

      We couldn't find what you're looking for
      We looked everywhere, but it doesn't exist. It may have been deleted. Unless, of course, the URL has a typo in it
      

      Steps to Reproduce

      1. Enable Space Bulk Conversion
      2. Publish page with legacy editor, to trigger the conversion
      3. Some pages will break

      Expected Results

      The conversion should work successfully and the page should load as expected

      Actual Results

      After the conversion when navigating to the page the below error will appear:

      We couldn't find what you're looking for
      We looked everywhere, but it doesn't exist. It may have been deleted. Unless, of course, the URL has a typo in it
      

      Workaround

      Currently there are 2 workarounds, however both can be fairly technical. Please don't hesitate to contact Support to assist with these workarounds:
      Workaround 1
      Revert page to the previous version before conversion. This is difficult because you'll have to manually configure the page history link with the below format:

      https://<SITE-NAME>.atlassian.net/wiki/spaces/<SPACE-KEY>/history/<CONTENT-ID>

      Workaround 2
      Recreate the page through the API. The below flow should work.

      1. View the problematic page with the REST API: https://<SITE-NAME>.atlassian.net/wiki/rest/api/content/<CONTENT-ID>
      2. Grab the HTML body storage of the page
      3. Create a new page with the Confluence Cloud V2 REST API: Create Page. You'll want to use the previously grab HTML body storage format to populate the new page.

              Assignee:
              Unassigned
              Reporter:
              Isaac Spann
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: