Posit Connect - Unable to read quarto extension #14771
DescriptionI am using Posit Workbench and am trying to publish a quarto document to Posit Connect. The document is using a custom extension in the I don't think this is the right place to discuss it, but I cannot find a similar forum for https://github.com/DOH-FAA3303/quarto-publish-error These are the steps I've taken: rsconnect write-manifest quarto --overwrite --package-installer UV template.qmd
rsconnect deploy manifest manifest.json Then it fails with 2026/08/13 16:59:16.753698480 [connect-quarto] Running 'quarto render'
2026/08/13 16:59:17.806101000 ERROR: Unable to read the extension 'two_pager'.
2026/08/13 16:59:17.806117801 Please ensure that you provided the correct id and that the extension is installed.I have tried to run Posit Publisher in Positron and checking the box to include the _extensions folder in the toml, but same error. If this is not the right forum, where can I request for help? |
Replies: 2 comments 3 replies
|
At first glance, I would say you are publishing a single document instead of a project by specifying the document, thus perhaps why everything else is lost. |
|
Resolved.. You need to write all files to the manifest like: rsconnect write-manifest quarto \
--overwrite \
template.qmd \
_extensions/my-extension/_extension.yml \
_extensions/my-extension/template.html \
_extensions/my-extension/styles.css \
_extensions/my-extension/template.texnote: UV would not work no matter what I tried, so I had to export the uv export \
--locked \
--format requirements.txt \
--no-hashes \
--output-file requirements.txtthen run rsconnect deploy manifest manifest.json That failed for me with this error: [ERROR]: 'utf-8' codec can't decode byte 0x80 in positon 10: invalid start byteI fixed it with rsconnect deploy manifest manifest.json --no-verifytl;dr - getting quarto to publish in posit takes some effort :( |


Resolved..
You need to write all files to the manifest like:
note: UV would not work no matter what I tried, so I had to export the
uv.locktorequirements.txt:uv export \ --locked \ --format requirements.txt \ --no-hashes \ --output-file requirements.txtthen run
That failed for me with this error:
I fixed it with
--no-verify