-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
Issue Summary
Include Page Macro breaks if the page is copied to another space
Steps to Reproduce
- Create a Page A and B.
- Add 'Include Page Macro' to the page A and add the content on page B.
- Copy the page A to another space.
Expected Results
The Include Page Macro shouldn't break.
Actual Results
The Inlude Page Macro breaks.
"*_Unable to render
The included page could not be found._*"
Workaround
Use Exceprt and Include except macro instead.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFCLOUD-72730] Include Page Macro breaks if the page is copied to another space
When including a page from same space then "space-key" is not persisted.
However if page A and page B would be originally in different spaces, then "space-key" is saved and it makes it possible to copy page from one space to another as expected.
BUT if you copy page A to the same space from where it includes page B, then the space-key is lost again and you cannot copy it successfully to other spaces.
Maybe omitting space-key for same space pages helps with moving/copying page-trees from one space to another, but that is a big MAYBE, because the desired outcome for those case is debatable.
<ri:page ri:space-key=“CIH" ri:content-title=“TITLE OF PAGE B” ri:version-at-save=“1" />
Only case for not having space-key, is when you want to MOVE a tree of pages that are including each-other. If you would have included page under some other parent or you would not want to move/copy that page, then include macro would still break.
Considering that when moving or updating the target page, that is included, then macro is updated in including page to update both page title and space-key information, then having this macro break or not track its included page when copying itself to different space, is surely a bug ant not a feature.
Same behavior if you simply use page links. Links to pages in the same space break if you copy the page in a different space.
Same behaviour in our Confluence Cloud instance, slightly different error message, but might be due to German localization?!
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!