Add ability to (optionally) render included content in the context of the INCLUDING page
GENERAL USE CASE: allow multiexcerpt include to render its content in the context of the page that is including the macro instead of in the context of the original excerpt page.
See where we addressed this same feature request. We added a useIncluderPageContext (“Use MultiExcerpt Include Page Context”) parameter to the MultiExcerpt-Include macro. We can do the same for Cloud. Keep the parameter name consistent for easy Server → Cloud migrations.
From a customer use-case for MultiExcerpt-Cloud:
On space A, I have an multi-excerpt macro with a page template I want to display on many spaces.
On space B and C, i use multi-excerpt-include to reference the page ins space A.
the page on Space A contains an "recently-updated" macro from atlassian.
On space B and C, i see those page from space A but not from B or C.
Is it a bug ?
Create a Support Ticket
Sounds great !
: I reopened this and returned it to the backlog. I thought about it some more and it seems that this could be a possibility if we created a new mode/type of excerpt include macro: one that renders not in the context of the original excerpt (source) page but in the context of the excerpt include (target) page. That way, any nested macro (like "recently-updated" would be included in the rendered content BUT would execute its logic in the excerpt include (target) page.
I will bring this to the attention of our lead developer so that I can see if this idea is a possibility with the current architecture of Atlassian Connect and our app.
Thanks for your explanation. That makes sense…
Any chance for my useCase to work with MultiExcerpt ?
: the MultiExcerpt Include macro renders content from the included (source) space. The nested macro was executed in the source space to give the render content.
I apologize for the late response. I found this "New Feature" item in our backlog. In general, it is best to start with a support ticket because the support queue is constantly monitored by a team of engineers. If some other type of item is opened in Jira, like a Bug or New Feature it can sometimes go unnoticed in the pile of the backlog. Sorry!