[1.16.0]
Update documenso to 2.5.0
Full Changelog
fix: mark document auth types for translation by @mKoonrad in #2331
fix: mark document visibility options for translation by @mKoonrad in #2330
refactor: simplify field dialog component by @catalinpit in #2369
feat: add audit logs to document details page by @Mythie in #2379
feat: add default recipients for teams and orgs by @catalinpit in #2248
fix: downgrade pdfjs-dist to version 5.4.296 and update react-pdf to version 10.3.0 by @KarloDerEchte in #2383
fix: dont flatten forms for templates by @Mythie in #2386
fix: security CVE-2026-22817 CVE-2026-22818 by @tedliang in #2390
fix: sync envelope state after direct link changes by @ephraimduncan in #2257
refactor: replace pdf-sign with libpdf/core for PDF operations by @Mythie in #2403
@andirahmat How big a document were you trying to sign? Could you try to sign a small pdf just with one page?
I've tried to reproduce the issue but had no luck.
First I installed v1.7.0, the signing certificate page was succesfully generated there, then I updated the app to v1.7.1, and signed a new document - Signing certificate page was attached as well.
Hello @CaeruleusAqua
@pepicrft linked the workaround here
@pepicrft said in Documenso does not come up after update to 1.6.0:
For anyone running into this, it seems the migration assumes that all teams have a subscription. Until the migration is fixed, you can workaround it by faking a subscription.
Either you can apply this yourself or you will have to wait until Documenso releases a new Update fixing this issue.
Hello @Isaac
This is the Cloudron Community.
Since you stated you are hosting Documenso on proxmox we are unable to assist you any further.
But since you found us, maybe Cloudron can help you to host Documenso so it works out of the box!
Seems like an app internal issue, but maybe some packaging side-effect, hard to tell without any server side logs.
Are you able to create signature fields using the UI itself?
As with the feedback from @CptPlastic at https://forum.cloudron.io/topic/12281/create-new-cert this shoud be solved then if you follow the adjusted docs https://docs.cloudron.io/apps/documenso/#signing-certificate
This should be fixed with package version 0.2.0 published by now. This will redirect the link from the success share card to the upstream project URL for https://documenso.com
https://git.cloudron.io/cloudron/documenso-app/-/commit/23d52ca75fb33ee10d1ad5ef965dc387ebb5f6c9
Mail template (with their company address) is hardcoded at https://github.com/documenso/documenso/blob/main/packages/email/template-components/template-footer.tsx#L22