-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
5.9.8, 1000.7.0
-
Severity 3 - Minor
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
The problem: If you request the content body using the content rest API, and the content contains macros, the macros don't work (in most cases).
The cause:
1 - Some macros don't explicitly list their web resource dependencies, and so the web resource is not included in the response from the API.
2 - Web resources that are included in the superbatch are excluded from API response, so if the super batch doesn't exist on the page, then javascript errors are thrown due to missing dependencies.
3 - Some macros assume a page load lifecycle that will have a load/ready event. When using the rest API this is often not the case.
- is related to
-
CONFCLOUD-52718 Code macro not rendering correctly when using content rest API
- Closed
-
CONFCLOUD-52785 Expand macro not working when using content rest API
- Closed
-
CONFCLOUD-52953 Mentions are not rendered correctly when using the content rest API
- Closed
-
CONFCLOUD-53010 Tasks lists are not rendered correctly when using the content rest API
- Closed
-
CONFCLOUD-52776 Sorting inline tasks does not work in Connect macros
- Closed
-
CONFCLOUD-53228 Images are returned with a relative path from the content API
- Closed
- relates to
-
CONFCLOUD-41551 Cannot render macros from content rest API
- Closed