Published Capable Site shows "PDF embed: the configured PDF could not be exported"
What you are seeing
A published Capable Site shows "PDF embed: the configured PDF could not be exported".
#Why it happens
Neither the linked file nor the attachment could be resolved when the site was built.
#What to do
Check the source still resolves and that the reader account used for the build can see the attachment, then re-deploy the site. Attaching the PDF to the page is the most reliable source for site publishing.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Get started page | Shown after install | - |
Approved external domains (Capable Suite | Capable Suite admin > Capable settings > Egress | - |
Edition | Capable Suite capability list | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Linked PDF size ceiling | 2.5 MB | A PDF fetched from a public web address is refused above 2.5 MB and the macro shows "This PDF is too large". Attachments do not go through the proxy and are not subject to this cap. The limit is not s |
#A few things that catch people out
In the Capable Suite, an admin cannot hide or disable PDF Embed from the Capabilities list, because it is a macro-only capability.
#Related
Externally hosted PDF still points at the original website after a site deploy, and breaks for some
The site build tries to copy the file into the published output and quietly falls back to
Adding the PDF's host to the Suite's approved domains made the embed stop working
An approved host is fetched directly by the reader's browser instead of through Capable's
Export and published sites
The rest of this family.
Found it? Good.
