Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-80110

Error creating a page using the "Create from template" macro

XMLWordPrintable

      Issue Summary

      Error creating a legacy page editor using a legacy template

      The following issue only occurs on Legacy Editor when trying to use a template with variables when a user tries to use the Create From Template macro.

      Steps to Reproduce

      1. Create a template using legacy editor
      2. Using the legacy editor add the button create from template macro on the page
      3. Provide the legacy template details in the macro window
      4. Publish the page
      5. Click the button to create the page using the template

      Expected Results

      Page to be created with no errors

      Actual Results

      When you click next it errors

      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

      Option 1: 

      • Remove the variables from the legacy template if feasible until the issue is resolved.

      Option 2 (Recommended): 

      • Convert these legacy templates and pages to new editor. 

      Kindly note that Templates & Pages from the Legacy Editor to the New Editor can only be converted if they contain only content that is supported in the New Editor.

      For details on which content is supported or not in the New Editor, please check out this document:

      Please check out this Community Post with more details regarding the Template Conversion:

      Finally, for Page Conversion, please check out this Community Post with more details

        1. screenshot-1.png
          screenshot-1.png
          350 kB

          Form Name

            [CONFCLOUD-80110] Error creating a page using the "Create from template" macro

            Edwin Del Bosque added a comment -

            We've identified 2 workarounds from issue PCS-350603:

            As a workaround, you can consider following two options:

            Option 1: 

            • Remove the variables from the legacy template if feasible until the issue is resolved.

            Option 2 (Recommended): 

            • Convert these legacy templates and pages to new editor. 

            Kindly note that Templates & Pages from the Legacy Editor to the New Editor can only be converted if they contain only content that is supported in the New Editor.

            For details on which content is supported or not in the New Editor, please check out this document:

            Please check out this Community Post with more details regarding the Template Conversion:

            Finally, for Page Conversion, please check out this Community Post with more details

            I hope the information provided above is helpful.
            Please let us know if you have any additional questions or queries and we will be happy to help!

            Edwin Del Bosque added a comment - We've identified 2 workarounds from issue PCS-350603: As a workaround, you can consider following two options: Option 1:   Remove the variables from the legacy template if feasible until the issue is resolved. Option 2   (Recommended) :  Convert these legacy templates and pages to new editor.  Kindly note that  Templates  &  Pages  from the  Legacy Editor  to the  New Editor  can only be converted if they contain only content that is supported in the  New Editor . For details on which content is supported or not in the  New Editor , please check out this document: What actually happens when your content is converted? Please check out this  Community Post  with more details regarding the  Template Conversion : Convert your old templates to the new editor! - Atlassian Community Finally, for  Page   Conversion, please  check out this  Community Post  with more details Convert legacy editor pages to the new editor! - Atlassian Community I hope the information provided above is helpful. Please let us know if you have any additional questions or queries and we will be happy to help!

              Unassigned Unassigned
              278c4f2d034c Pavani
              Affected customers:
              8 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: