"No space with key" error
Confluence Cloud: Multi Excerpt Include dialog shows the following (including excerpts from the same space):
Page intermittently renders the includes (currently does not) and fails to render code portions of the excerpts when formatted with the Expand macro.
Source page for includes:
Create a Support Ticket
We have pushed out a fix to correct the ":" in space name issue also. Marking this as resolved.
OK Great! And yes I understand how that would be confusing. We are updating our docs and will hopefully be pushing a fix for that some time next week or sooner.
Thank you for your interest in the MultiExcerpt plugin. If you are happy with the plugin please consider leaving a quick review on the MarketPlace here:
Good reviews help us continue to add features and fix up the AddOn when Atlassian "evolves" their platform which is frequently!
Done & working.
I had suspected the same, and first tried SPACE NAME: Quickstart: <page title>, but that didn't work. Was further confused by the fact that the content would intermittently render, something we see in Confluence often as a function of caching behaviors. Anyway thanks for the info & followup.
We have figured out what the problem here is, we have a "workaround" and are looking for a more permanent solution.
The issue here is that the colon ":" in the 'page name is what Confluence uses to denote a 'Confluence Space Key".
A page name could be: "Helpful Information"
A page with that name in another space with space key of "FUN" would be denoted in Confluence as: "FUN:Helpful Information"
In this case "FUN" is the space key. But if the name of the page is acutally "FUN: Helpful Information", then Confluence gets confused.
We are currently looking at a fix for this.
Workaround: If you are able to change the name of the page with the "multiexcerpts" to not have a colon ":" in the pagename, this will all work.
For example changing: "QuickStart: Creating a Platform User Account"
"QuickStart Creating a Platform User Account"
I'm downgrading the priority of this from Blocker as its not the app failing, but specific syntaxt handling we need to remedy if possible. However we ARE actively working on this right now.
Thank you for this bug report. We are working on it right now. We acknowledge its a Blocker.