Published site page shows an export note where a markdown document should be
What you are seeing
A published site page shows an export note where a markdown document should be.
#Why it happens
When the site was built, Capable could not find the document's content. It tried the source URL, an attached copy, a copy stored on the page and a search fallback, and none of them worked. This usually means the source URL could not be reached at that moment and there was no stored copy to fall back on.
#What to do
Give the macro a copy stored on the page, or an attached file, as well as the URL. Or fix the source URL. Then publish the site again.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Space settings → Space Capability Settings | - | Auto shows the Markdown entry in the page byline only when the page already carries markdown. Always shows it on every page in that space. Never hides it there. |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Large-document scroll mode | 500,000 characters | Past this the document shows '⚠️ Large content detected. Rendering in scrollable mode.' and sits inside a fixed-height scroll box instead of showing in full. |
Version history entry limit | 50 | Beyond 50 versions the panel shows 'Limited to the last 50 entries'. |
#Related
Exported Word or PDF shows raw markdown source in a code block
The markdown source in a fenced code block, never rendered prose.
Published Capable Site page looks different from the Confluence page
Raw HTML is off there too, and diagram fences come out as styled code blocks rather than d
Export and published sites
The rest of this family.
Found it? Good.
