I noticed in earlier versions the new(ish) PDF editor does not allow saving in the online editor (only save a copy).
Is there a plan to implement saving in the same structure as other editors (sheets, presentations, etc)? I’m currently running 8.11
In the meantime, is there perhaps a way to suppress the save copy message and run my own JavaScript to capture the save event and then run my own logic by creating a copy of the file myself and saving it through my own integration?
In new version of Document Server we have enhanced possibilities of saving PDF files back to storage. Also, collaborative mode was implemented to PDF editing.
Please update your instance and share your thoughts.
Thanks for coming back with this - I was watching the Webinar today actually!
Unfortunately I can’t seem to upgrade (ubuntu):
Reading package lists…
Building dependency tree…
Reading state information…
postgresql is already the newest version (14+238).
expect is already the newest version (5.45.4-2build1).
redis-server is already the newest version (5:6.0.16-1ubuntu1).
nano is already the newest version (6.2-1ubuntu0.1).
rabbitmq-server is already the newest version (3.9.13-1ubuntu0.22.04.2).
wget is already the newest version (1.21.2-2ubuntu1.1).
nginx-extras is already the newest version (1.18.0-6ubuntu14.5).
0 upgraded, 0 newly installed, 0 to remove and 90 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up onlyoffice-documentserver (8.2.0-143) …
ERROR: can’t connect to postgressql database
dpkg: error processing package onlyoffice-documentserver (–configure):
installed onlyoffice-documentserver package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.35-0ubuntu3.8) …
Errors were encountered while processing:
onlyoffice-documentserver
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
First time around, the script asked me if I wanted to update default.json to the new version.
When I did, it broke (the database access message you see above, even after I enter the correct host, name, password, etc)
So this then I tried to keep my existing default.json which allowed me to complete the upgrade.
However, as you can imagine, the old default.json didn’t work as it omitted many of the new requirements for 8.2
So at this point, I replaced with the new version of default.json (after the install completed), suddenly everything works fine!
My guess (and it’s only a guess), is the install script somehow ignores and connection strings in local.json and therefore only uses whatever is hardcoded in the package’s default.json causing the postgres connection issue.