-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
5.7
-
1
-
Severity 3 - Minor
-
Summary
Using the Blog Post Macro fails when using it in the Default Welcome Message template.
Steps to Reproduce
- Go to Confluence Admin
- Choose Global Templates and Blueprints
- Choose Edit next to Default Welcome Message
- Add the Blog Post Macro
- Save
Expected Results
The blog post macro displays as normal.
Actual Results
The Blog Post Macro does not render, and displays the following error:
$helper.renderConfluenceMacro("{blog-posts:space=@global|content=excerpts|max=5}")
There are no errors present in the logs.
[CONFSERVER-38095] Blog Post Macro fails when used in the Default Welcome Message template
QA Demo Status | New: Not Needed [ 14332 ] | |
QA Kickoff Status | New: Not Needed [ 14236 ] | |
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: affects-server spaces | New: affects-server cleanup-seos-fy25 spaces |
Workflow | Original: JAC Bug Workflow v3 [ 2903634 ] | New: CONFSERVER Bug Workflow v4 [ 2998244 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2802274 ] | New: JAC Bug Workflow v3 [ 2903634 ] |
Workflow | Original: JAC Bug Workflow [ 2718929 ] | New: JAC Bug Workflow v2 [ 2802274 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2383133 ] | New: JAC Bug Workflow [ 2718929 ] |
Status | Original: Open [ 1 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2276418 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2383133 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2218759 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2276418 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center