-
Bug
-
Resolution: Won't Fix
-
Highest
-
19
-
Severity 2 - Major
-
35
-
-
Warranty
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
- Create a template using legacy editor
- Using the legacy editor add the button create from template macro on the page
- Provide the legacy template details in the macro window
- Publish the page
- 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
- causes
-
-
- Gathering Impact
-
[CONFCLOUD-80110] Error creating a page using the "Create from template" macro
| Remote Link | Original: This issue links to "Page (Confluence)" [ 984854 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 984854 ] |
| Link | New: This issue causes CONFCLOUD-80340 [ CONFCLOUD-80340 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 969334 ] |
| UIS | Original: 34 | New: 35 |
| Component/s | New: Page - Editor - Legacy (TinyMCE) [ 47611 ] |
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Description |
Original:
h3. 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. Based on our team’s investigations, we found no direct changes made to the affected component. The issue is likely a recent side effect of changes introduced by another team in the legacy editor. Essentially, while the template variables are being parsed correctly in the endpoint, there’s a point during the draft creation flow where no {{spaceKey}} is assigned to the query. This causes the draft creation to float without a space, ultimately resulting in a 404 error.The root cause has been particularly challenging to pinpoint, especially given the complexities of the legacy editor. This is also an error that is only reproducible in staging and prod and not locally/dev, which has made the investigation slower. h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |
New:
h3. 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. h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |
| Description |
Original:
h3. Issue Summary
Error creating a legacy page editor using a legacy template Error is seen both when creating a page using the template and using the *create from template* button. The following issue only occurs on {*}Legacy Editor when trying to use a template with variables{*}. Based on our team’s investigations, we found no direct changes made to the affected component. The issue is likely a recent side effect of changes introduced by another team in the legacy editor. Essentially, while the template variables are being parsed correctly in the endpoint, there’s a point during the draft creation flow where no {{spaceKey}} is assigned to the query. This causes the draft creation to float without a space, ultimately resulting in a 404 error.The root cause has been particularly challenging to pinpoint, especially given the complexities of the legacy editor. This is also an error that is only reproducible in staging and prod and not locally/dev, which has made the investigation slower. h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |
New:
h3. 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. Based on our team’s investigations, we found no direct changes made to the affected component. The issue is likely a recent side effect of changes introduced by another team in the legacy editor. Essentially, while the template variables are being parsed correctly in the endpoint, there’s a point during the draft creation flow where no {{spaceKey}} is assigned to the query. This causes the draft creation to float without a space, ultimately resulting in a 404 error.The root cause has been particularly challenging to pinpoint, especially given the complexities of the legacy editor. This is also an error that is only reproducible in staging and prod and not locally/dev, which has made the investigation slower. h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |
| Description |
Original:
h3. Issue Summary
Error creating a legacy page editor using a legacy template Error is seen both when creating a page using the template and using the *create from template* button h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |
New:
h3. Issue Summary
Error creating a legacy page editor using a legacy template Error is seen both when creating a page using the template and using the *create from template* button. The following issue only occurs on {*}Legacy Editor when trying to use a template with variables{*}. Based on our team’s investigations, we found no direct changes made to the affected component. The issue is likely a recent side effect of changes introduced by another team in the legacy editor. Essentially, while the template variables are being parsed correctly in the endpoint, there’s a point during the draft creation flow where no {{spaceKey}} is assigned to the query. This causes the draft creation to float without a space, ultimately resulting in a 404 error.The root cause has been particularly challenging to pinpoint, especially given the complexities of the legacy editor. This is also an error that is only reproducible in staging and prod and not locally/dev, which has made the investigation slower. h3. Steps to Reproduce # Create a template using legacy editor # Using the legacy editor add the button *create from template* macro on the page # Provide the legacy template details in the macro window # Publish the page # Click the button to create the page using the template h3. Expected Results Page to be created with no errors h3. Actual Results When you click next it errors {noformat} 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 {noformat} h3. 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: - [What actually happens when your content is converted?|https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/#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|https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117] Finally, for *Page* *Conversion, please* check out this *Community Post* with more details * [Convert legacy editor pages to the new editor! - Atlassian Community|https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943] |