-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Macros - Page Properties
-
None
-
1
-
Minor
Issue Summary
A Content Properties Report macro (i.e. Page Properties Report macro) containing values rendered by Insert Excerpt macros displays correctly in the editor and outside some vendor macros (for example, Stiltsoft's Table Filter macro). However, rendering the report through the Confluence REST API’s export_view representation returns errors in the cells containing Insert Excerpt macros. Furthermore, the Insert Excerpt macros only return these errors if they are referencing Excerpt macros from the same page.
Steps to Reproduce
- Create Page A, the source content with an Excerpt macro and a Page Properties table containing an Insert Excerpt macro referencing that excerpt.
- Create a new draft for Page A.
- Add an Excerpt macro to Page A with the text "John Smith".
- Add a Page Properties macro outside of the previous excerpt macro to Page A.
- Provide a key for a row of the Page Properties macro, for example "Name". For the value, add an Insert Excerpt macro that references the Excerpt made in Step 1.2.
- Publish Page A.
- Create Page B. Edit it to contain a Page Properties Report macro that lists Page A as a result.
- Nest the Page Properties Report macro inside a Table Filter macro and publish Page B.
- As an alternative to Step 3, request the published page’s export_view representation with a REST API request: GET /wiki/rest/api/content/{pageId}?expand=body.export_view. Inspect the report cells in body.export_view.value.
Expected Results
The export_view response contains the resolved excerpt content in the Page Properties Report cells, consistent with successful native rendering.
Actual Results
Report cells containing Insert Excerpt macros display the following error, which is also present in the REST API’s export_view response:
Error rendering macro 'excerpt-include' : No location was provided
Workaround
Move the excerpts from Page A to a different page.