New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File saving fail after a read only open (share) ("Empty Callback commandSfcCallback") #914
Comments
Moving to |
If there is any change or indication of how the error of not saving the document can be corrected |
Hello, I am having the same issue so many times when I share a document. I would be very greatful if anyone had a solution to fix this. Sometimes I have to close my current session, wait for a few minuts and come back, then my modifications are back... |
After some discussion we detect that issue in DocumentServer itself and should fixed after ONLYOFFICE/server@0a14695 Also some other case in #45406 in our private bug tracker |
DocumentServer v5.6.0 is released and this problem should be fixed |
for me, it is not .. Nextcloud: 21.0.1 Same behaviour |
Please note that Community Document Server was developed by Nextcloud Team, if you have any issues with it, please contact them in the appropriate GitHub repository. If you are using our official method of integration (Nextcloud + dedicated Document Server instance as per our installation guide), we will be glad to answer your questions. Please see more info on our forum. |
Hello,
I've noticed a bug.
My current version is Nextcloud 18.0.4 (FPM custom installation + NGINX) + Document Server 5.5.3 on docker, all in debian. My browser is Chromium 81 Ubuntu.
Here a scenario to reproduce the bug :
And then, when I go to container logs, I have :
==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2020-05-26T22:34:01.702] [WARN] nodeJS - Empty Callback commandSfcCallback: docId = 554837848
[2020-05-26T22:37:54.030] [WARN] nodeJS - Empty Callback commandSfcCallback: docId = 554837848
Thank you for your great job !
Houman
The text was updated successfully, but these errors were encountered: