Edits and changes made in Onlyoffice are not synced into Nextcloud

[timo12357]

Issue

Edits and changes made in Onlyoffice are not saved into Nextcloud and the next sync from Nextcloud to Onlyoffice destroys all changes made in Onlyoffice. This results in loss of work.

Expected Behavior

Edits and changes written in Onlyoffice sync to the local desktop environment and the changes done in the desktop environment sync to OnlyOffice

Actual Behavior

Files stored in the local desktop environment are synced flawlessly to Nextcloud. Onlyoffice opens them flawlessly and lets the user edit the document. After saving the document and or logging out from nextcloud changes are kept in OnlyOffice cache and never written to the actual document. When user opens same document from the desktop the changes have disappeared. If user saves the document with a small change, this change is synced to OnlyOffice overwriting the changes in the cache.

Possible Fix

Write cache data to file regularly and frequently. Recognize when user leaves Onlyoffice or closes file and write cache to file. In short: Copy the functionality of Google Docs.

Steps to Reproduce

1. Use a desktop wordprocessor and create a document in a NextCloud synced folder in your desktop environment
2. Log onto the Nextcloud web UI and open the file with OnlyOffice.
3. Ask colleague to do the same
4. Make changes in document
5. Exit document
6. Open document with desktop wordprocessor from local NextCloud synced folder.
7. Notice that the changes never were saved to the file in NextCloud,.
8. Open file in OnlyOffice from the Nextcloud web UI to notice changes are still there
9. Close OnlyOffice
10. Make minimal change in the desktop wordprocessor and save file locally.
11. Let NextCloud sync
12. Open file in OnlyOffice from the Nextcloud web UI to notice all changes made in OnlyOffice have been lost and overwritten with those made in the desktop environment
13. Feel despair.

Context

We just lost 2 days worth of expensive work made by our consultant. This is becoming very expensive to us!

Your Environment

• Nextcloud 18.0.3
• OnlyOffice Community Server bundled with NextCloud 18
• Nextcloud desktop client 2.6.4 Linux
• Nextcloud desktop client 2.6.4 Mac

Edit: Tried also this cronjob proposed by @googol42 but it does NOT solve the issue

• • • • • php -f /var/www/yourdomain/occ documentserver:flush

[RNCTX]

This was developed for private home users who can't install a docker image but do occasionally want to edit a DOCX or PPTX file. Nothing more.

That's not what your presentation with marketing and management execs from both companies involved said.

Changing this is very hard (we already put in 1 year just to develop this). To fix this problem (and similar issues you inevitably have to start changing ONLYOFFICE itself and without a team of at least 6-7 full time people, it is impossible to maintain that. We're not going to for this. This was a gift to home users, nothing more.

No, you get free QA from the deal, not to mention people developing lots of free third party extensions that your paying customers surely use in droves. There's also the fact that all of these individual users drive people to pay for your mother company's VOIP software and your third party partners' software.

So, if you're not a private user and this doesn't work for you, use the docker, use Collabora, buy ONLYOFFICE and get packages - loads of options. Don't ever expect us to support this for anything other than a casual, private home use case.

I don't think anyone is complaining about beta tools not working. If you release something marked as beta that doesn't work out of the box people are happy to beat on it and give you feedback, and maybe even some code to fix bugs they find, but if you have a big marketing event with executives from two for-profit companies touting a new feature, release that feature to the public, and then two weeks later the feature doesn't work, what do you expect other than bug reports and people digging into the code that you release to the public? Is that not what you wanted? See free QA point above.

[timo12357]

Please understand something: This was developed for private home users who can't install a docker image but do occasionally want to edit a DOCX or PPTX file. Nothing more.

I think it would make a lot of sense to update the Nextcloud Hub marketing material with this info. Just looked through the launch video and there was nothing about home use of Onlyoffice in it. I never read this anywhere and have totally missed this point until now.

I am afraid a lot of SME and start-up users like us, upgraded to NC 18 thanks to the great marketing for Nextcloud Hub. Onlyoffice was the Unique Selling Point USP of the campaign. Had we known the Onlyoffice integration is NOT meant for production use, we would still be at NC 17.x.x.

If the bug can not be fixed, at least please update the Nextcloud homepage to avoid more businesses from losing money on this. We certainly did.

[jcgerhard]

Please understand something: This was developed for private home users who can't install a docker image but do occasionally want to edit a DOCX or PPTX file. Nothing more.

What? I can‘t really believe to read such a statement! If this is actually true, it would destroy a big part of the credibility that was built up during the last years. I had switch to the nextcloud platform entirely because of this big new office feature. The complete integration is superfluous if noone is able to save even one simple change...and that‘s what it is for me. Even „only“ modifying an existing document does not work because the changes won‘t be flushed from the document server and wrote to the nextcloud file. It only works if I do an occ documentserver:flush manually.

I simply hope that this will be fixed as soon as possible! And do yourself a favour and don‘t risk to put off long-standing users with such attitudes. That‘s not what nextcloud stands for...I think!

[stweil]

I've tagged it as a bug, but there is nothing we can do. ONLYOFFICE has to fix this and they said they will so now we just have to wait.

Maybe the real picture is a bit different. See issue #110 which documents my latest findings. Basically the automated flushing of changes made in ONLYOFFICE works quite nice - as long as no problems come into the way. Such problems are currently caused by any document which does not have an owner (-> group folders), and they can also be caused by at least one more kind of errors in documents. The good news is that the first cause should be fixed in one the next stable releases, because there is already a fix in master. The bad news is that any such problem not only stops flushing of the affected file, but also of any file which comes later in the queue. This should be made more robust. Using manual flushing with occ helps to detect such problems because it prints an error message.

[joequant]

If anyone need medical supplies or has sources of medical supplies, please ping me. I'm using onlyoffice/nexthub to coordinate this.

If Onlyoffice/Nexthub can't or won't put resources into this, I will. That's the beauty of open source, and that's why I put my stuff on Onlyoffice/Nexthub rather than Google docs or Microsoft. If I put this in google docs, and I run into a problem, I'm screwed. With Onlyoffice/Nexthub if I run into a problem and the developers are unresponsive, I go in and fix it myself.

The reason that this is a critical issue is that I'm using Nexthub/Onlyoffice to set a team to deliver COVID products from China to the rest of the world. The reason this came up is that we have a set up standardized forms which we've developed to track suppliers, and we had a situation where we modified the form, and then the modifications didn't appear.

Now that I understand what is going on, we can work around the issue in the short term (i.e. just wait five minutes for the files to sync) If time permits, I can open up an API that gets allows a manual sync. What I have in mind is to extend occ to just save active files, and then have a simple API that calls that and sees the response.

[joequant]

The problem with marketing this to just "casual users" is that anyone that just wants to edit a few docx or pptx will just use Google sheets or Office 365, and not bother installing anything. If I just wanted to edit a few docx files, I'd use closed source stuff. The reason why Onlyoffice/nexthub is useful to me is that I can modify it to do weird stuff.

As far as resources go, I'm in the process of applying for a grant from the Hong Kong government develop platforms for high energy physicists and quants. The thing about scientists and traders is that you have to deal with a ton of paperwork, and there is a fun chicken and egg because to apply for the grant you need a scary amount of paperwork which I'm using Onlyoffice to put together. I'm also supplementing my income by doing medical supply deals, which again requires a ton of paperwork.

Also the reason I'm not using a full blown onlyoffice server is that its a resource hog. You'd like to have the office server run on the same machine you are doing computes, and the app is delightfully slim which means that you aren't hogging the memory or cpu for other things.

I'm fairly certain that the bug happens because the update throws an exception which stops the commit. It works for me now, but I had to dump out the old files, and reload them. The old instance was giving me an exception when it was processing commits.

[joequant]

Okay before I open up the patient, let me know if this makes sense

1) add a command documentserver:flushinactive which flushes inactive pages 2) add an entry in route.php which allows the user to flush the unsaved changes 3) reduce the timeouts so that they go from 100 seconds to something more like 15 4) change documentserver:flush so that if it gets an exception that it continues to the next page

The idea is that once we have this in place someone should be able to trigger a flush by calling the route entry and hopefully you see the debugging output. I just started looking at the code so I'm not sure how you'd go about triggering a call externally.

[joequant]

On second thought, it looks like it would be better to modify the 'documentserver:flush' command to have a flag "--inactive-pages"

[timo12357]

@joequant Joseph, you are a modern day hero!

[jospoortvliet]

Great work @joequant ! That is very helpful.

Maybe the real picture is a bit different. See issue #110 which documents my latest findings. Basically the automated flushing of changes made in ONLYOFFICE works quite nice - as long as no problems come into the way. Such problems are currently caused by any document which does not have an owner (-> group folders), and they can also be caused by at least one more kind of errors in documents. The good news is that the first cause should be fixed in one the next stable releases, because there is already a fix in master. The bad news is that any such problem not only stops flushing of the affected file, but also of any file which comes later in the queue. This should be made more robust. Using manual flushing with occ helps to detect such problems because it prints an error message.

Thanks for the extensive analysis. I hope this can help get this fixed sooner. I would love to be able to say that we can work on this from our side today, but we're currently understaffed and overloaded already so I'm afraid that this will have to rely on help from the community (like @joequant !) for the time being, until we have time again :-1: the Corona times are hard on us too, causing more work while it limits some of our engineers from working full time. We're trying to offload things to partners where we can, hence the announcement from today, by the way.

What? I can‘t really believe to read such a statement! If this is actually true, it would destroy a big part of the credibility that was built up during the last years. I had switch to the nextcloud platform entirely because of this big new office feature.

We make no fake promises. Our integrated office solutions (two of them, three if you count this one) are of course perfectly suitable for enterprise and large scale work. But you have to pick the right solution for the job. We simply added one more option for home users that is easier to install but does not scale.

As I said above and as we wrote in the announcement, the community server makes ONLYOFFICE easier to install. Nothing more, nothing less. See also our blog about how to install it: https://nextcloud.com/blog/how-to-install-onlyoffice-in-nextcloud-hub-and-new-integration-feature/

Let me quote:

The Community Document Server is aimed at home use. Just like traditionally installed Document Server, it can be upgraded to ONLYOFFICE Integration Edition, a scalable enterprise solution with professional tech assistance.

We didn't and don't promise anything about scalability or suitability for large scale use - and there's even a limit built in to 20 concurrent connections. Everyone was and is upset about that, but also upset that we didn't communicate that it doesn't scale. Hum, can't make everyone happy, clearly.

I've updated the readme (https://github.com/nextcloud/documentserver_community/pull/112 comments welcome) to make this more clear.

We are, by the way, working on making this also possible for Collabora. It simply adds another, easier way of getting it to work, but it absolutely has issues and limitations and those are inherent to the technology we use. The Collabora version will ALSO scale less well as the docker version, which in turn scales less well than the packages that Collabora offers customers (same with ONLYOFFICE).

The complete integration is superfluous if noone is able to save even one simple change...and that‘s what it is for me. Even „only“ modifying an existing document does not work because the changes won‘t be flushed from the document server and wrote to the nextcloud file. It only works if I do an occ documentserver:flush manually.

I simply hope that this will be fixed as soon as possible! And do yourself a favour and don‘t risk to put off long-standing users with such attitudes. That‘s not what nextcloud stands for...I think!

That is a bug, and of course should be fixed, but that is separate from the fact that the community document server has serious limitations and always will.

[Ulch]

Thanks to all of you, especially @joequant, for your explanations and for your efforts to resolve this issue!

Just one point, @jospoortvliet, on your explanations: I understand that the community server is meant to serve as a solution for home users and that it is not designed to scale. In my case, however, the problem occurs even if I work on as a single user on a document on an NC instance with only three user accounts. So, in my case the problem is not really related to scale, but seems to be a more general problem.

[jospoortvliet]

In my case, however, the problem occurs even if I work on as a single user on a document on an NC instance with only three user accounts. So, in my case the problem is not really related to scale, but seems to be a more general problem.

As I said:

That is a bug, and of course should be fixed, but that is separate from the fact that the community document server has serious limitations and always will.

[L3o-pold]

In my case, however, the problem occurs even if I work on as a single user on a document on an NC instance with only three user accounts. So, in my case the problem is not really related to scale, but seems to be a more general problem.

As I said:

That is a bug, and of course should be fixed, but that is separate from the fact that the community document server has serious limitations and always will.

Even with ONLYOFFICE Developer Edition the bug is here, and the product is sell as production ready!

[Joe7new]

In my case, however, the problem occurs even if I work on as a single user on a document on an NC instance with only three user accounts. So, in my case the problem is not really related to scale, but seems to be a more general problem.

As I said:

That is a bug, and of course should be fixed, but that is separate from the fact that the community document server has serious limitations and always will.

No problem with limitations - but basic functions should work reliably !! (or maybe it's better to fix obviously existing bugs before adding it as 'official app' to nextcloud or mark it as experimental or for private use only or something else!)

To avoid misunderstandings: I like Nextcloud very much and thanks for the great product !!

But- sorry : In my opinion the business features of nextcloud are the same as for community (without support). And in business environment its not possible to use that apps ! How can I know that official apps of nextcloud are only for 'private' use ? And it can't be user-friendly to execute occ-commands before to make it work. Sometimes it's better to have less features that work reliably ! (the problem of owncloud was exactly that : A huge amount of features but buggy - sometimes less is more; don't make the wrong way owncloud did at the beginning..) Sorry for my comment, but I could not hold it back.. kind regards, Joe

[laryllian]

Same here, we used it with two users only and a total of 8 hours work was lost just today – no recovery possible. I love Nextcloud, but if a feature is beta, please just call it that, so users are aware.

Trust is hard earned but easily lost, sad but true also here.

[Bolli84]

Option for a workaround: Save the File with "Save file as...". Then the new files is successfully synced into cloud, even with Group-folders.

Quick-fix for workaround would be: Save the File with "Save as..."

Modification needed: "Pick-folder-dialog" needs to be changed to include "Pick-folder-and-files", or simply allow tto choose the filename and replace the existing file.

[joequant]

Also one workflow that I think will work for me is to install occweb, and then that command

documentserver:flush --inactive

to force a flush.

This might be too much for people that aren't used to CLI's, but one quick workaround is to have a button somewhere that flushes the changes.

Also one of the reasons that this is a frustrating bug is that it happens silently. Something that will help is if there is some log file that can be alert the user if there is a problem with a save. What I think the root problem is is that because all of the saves are happening in the background, if something breaks, it just happens silently.

[joequant]

Also about business models. Nextcloud/OnlyOffice seems to be working on a "community/enterprise" model where you have a light-weight community edition and make money from a heavy weight enterprise edition. This is a very tricky business model to get right.

One problem with heavy/light is that enterprise is moving toward containerization, and one reason that the document server is very nice is that I can spin off a five or six document servers on a single machine. Once you have a situation where people are running containerized systems or mobile systems, then having a heavy system won't work well.

The other thing is that Moore's law hits you. The way that it worked in the past was that CPU/memory was getting faster. So you charge early adopters a ton of money so that they can run expensive CPU's that can crunch big systems. The trouble is that Moore's law has hit a wall and the future is large numbers of lightweight systems.

The two business models that I'm working on are:

1) the plumber/mechanic model. I'm trying to get lots of people to use the system so that if they need customer support or something fixed then they can pay me.

2) the public goods model. I'm in the process of applying for a grant from the HK government to work on a system that includes nextcloud, and the idea is to give this away for free since I'm being paid in part by public money, so anything I come up with gets released so that anyone can use it.

It turns out that there is a virtuous cycle here. Running an SME and applying for grants requires TONS of paperwork, and so I need a system where I can efficiently do paperwork.

[jospoortvliet]

Also about business models. Nextcloud/OnlyOffice seems to be working on a "community/enterprise" model where you have a light-weight community edition and make money from a heavy weight enterprise edition. This is a very tricky business model to get right.

One problem with heavy/light is that enterprise is moving toward containerization, and one reason that the document server is very nice is that I can spin off a five or six document servers on a single machine. Once you have a situation where people are running containerized systems or mobile systems, then having a heavy system won't work well.

With heavy/light you mean the scalability of a single system? Containerization is just one way to scale, there's no reason why that is more heavy or light. Depending on the app, containerization might be useless to 'scale up' - it won't help you have more people in a single document editing session unless you let different document servers talk to each other, for example. Also, this isn't related to the business or enterprise model, rather than the tech itself and sometimes programming language.

Nextcloud is the opposite of OO in that regard, btw, weird you lump them together - Nc's app servers are 100% independent thanks to PHP and thus super scalable with containers.

The other thing is that Moore's law hits you. The way that it worked in the past was that CPU/memory was getting faster. So you charge early adopters a ton of money so that they can run expensive CPU's that can crunch big systems. The trouble is that Moore's law has hit a wall and the future is large numbers of lightweight systems.

Only if the need and cost of synchronization between instances is low. Nextcloud is exactly the lightweight system you describe. Each application server is independent. But the database and storage are not, they are the limiting factor. With Global Scale you work around that, that is perfectly containerizable. But I think that generally there is an 'ideal' point of size for an app: 1000x 100 containerized user instances might be less efficient than 10x 10.000 user instances, for example, but 10x 10.000 can be more efficient than 1x 100.000. Every app has a different point where containers make sense.

Anyhow, it isn't related to business model - containers are just one way to scale up, and only works for some things. Just like microservices. Not everything is a nail just because you have a hammer and really like it ;-)

The two business models that I'm working on are:

1. the plumber/mechanic model. I'm trying to get lots of people to use the system so that if they need customer support or something fixed then they can pay me.
2. the public goods model. I'm in the process of applying for a grant from the HK government to work on a system that includes nextcloud, and the idea is to give this away for free since I'm being paid in part by public money, so anything I come up with gets released so that anyone can use it.

It turns out that there is a virtuous cycle here. Running an SME and applying for grants requires TONS of paperwork, and so I need a system where I can efficiently do paperwork.

Yes, there are companies that run entirely on this 'business model' (trying to get gov't money) but imho they produce little in terms of common good - the customer is the grant system, NOT the end user (why whould they care about end users if they don't pay them?.

The plumber/mechanic model (that is a good comparison, btw, hope you don't mind if I use that) has as downside that it is essentially consulting: you get paid to do exactly what the customer wants. It is the definition of the innovation trap: your existing customers determine what you do meaning you'll never extend the product with anything new that would be nice for other customers as they are not (yet) paying you.

For example, we would NEVER have developed this document server if we had the plumbers model as business model. Or Talk. Or calendar. Or almost anything ;-)

So yes, you're right that our business model is HARD. But it is the only one that allows you to build a product that does anything interesting and keeps up with changes in the market, rather than endless dead ends of fossilized products that serve an existing, legacy customer base.

As I said, I worked on a blog about this for opensource.com - it isn't published yet but my draft is here: https://cloud.nextcloud.com/s/f7nZzaEokqLGEpe

[Bolli84]

Update on my installation with Nextcloud 18.0.4 repair the issue. Now the file is synced back after some minutes.

[timo12357]

This sounds encouraging! Anyone else who can test and confirm?

[dominikhaczek]

This sounds encouraging! Anyone else who can test and confirm?

Ubuntu 18.04 Nextcloud 18.0.4 still not working for me, I even reinstalled documentserver_community app

[FreemoX]

This sounds encouraging! Anyone else who can test and confirm?

Ubuntu with the newest updates, including Nextcloud 18.0.4; functionality seems to be ok after "quick" tests (multiple users editing on the same document simultaneously for one hour). Still too early to declare it as stable enough for critical work, but I see none of my previous issues so far (User ghosting lock-out, missing letters/words/formating, "fast" collaboration sync issues, etc). Breaking network connection and reconnecting didn't drop any information written to the document while being "offline" either. Going to perform some more tests over the weekend, but would be nice if more people could perform some tests too (restrict Onlyoffice to certain test users and edit a new test document).

@dominikhaczek could you post some more information about your issues? Could be a bad configuration

[timo12357]

What fix did they pull in to fix this? edit: apparently the bug is still there and unfixed?

[sbellm]

Ubuntu 18.04 Nextcloud 18.0.4 still not working for me!

[schniepp]

It is also not working for me. 1) Here is what I did: upgraded NC to 18.0.4. 2) Opened a *.docx file with a 5 day-old timestamp using the OnlyOffice app. 3) Changed 1 character in this file. 4) Closed OnlyOffice using the "X" in the nextcloud bar 5) Checked the timestamp of the file: unchanged. Also no version of the file was created on NC 6) Downloaded the file and opened in Libreoffice (desktop app). The added character was not there. In other words, the file did not get updated. 7) Opened the file again in the OnlyOffice in NC, and the added character was there again!

I think the (quite scary and dangerous) behavior is exactly in line with what has been described before. To conclude, on my end, the 18.0.3 ⇒ 18.0.4 update of NC did not make a difference.

[stweil]

So you should run occ documentserver:flush to see what goes wrong. Chances are high that some other file is damaged and blocks the flush process.

[joequant]

Also if that's the problem, then I have a proposed fix that causes the flush to continue to try to save files even if one file has issues.

On Tue, Apr 28, 2020 at 1:52 PM Stefan Weil notifications@github.com wrote:

So you should run occ documentserver:flush to see what goes wrong. Chances are high that some other file is damaged and blocks the flush process.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nextcloud/documentserver_community/issues/100#issuecomment-620395842, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWGAGOBDQD256JE6JUJLWTROZVIVANCNFSM4LT7KQHQ .

[fabiangebert]

occ documentserver:flush yields

Uncaught TypeError: Cannot read property 'b8d' of undefined          

[joequant]

What I think is happening is that the doc server has problems parsing one file and then stops trying to save further files. #113 changes the code to continuing saving. There will be one file that is not savable but it will save the remaining files.

Here's a question....

I noticed the problem when I tried to import non-onlyoffice files. Could the parser be choking over a msword file that is imported but is missing some tag that onlyoffice is expecting?

[fabiangebert]

@joequant - I think we should try to address the issue rather than making the cron skip files it cannot persist. Does anyone of you guys suffer from an issue other than #88? In other words, does occ documentserver:flush produce output other than

Uncaught TypeError: Cannot read property 'b8d' of undefined          

If so, we could set up dev environment, reproduce the bug and see if we can fix the Document Server Javascript.

[joequant]

Agreed, but it might be a good idea to put in a backup to make the system more robust.

FWIW, this was the error I got a few weeks ago, when I ran into this non-save issue.

On Tue, Apr 28, 2020 at 4:02 PM Fabian Gebert notifications@github.com wrote:

@joequant https://github.com/joequant - I think we should try to address the issue rather than making the cron skip files it cannot persist. Does anyone of you guys suffer from an issue other than #88 https://github.com/nextcloud/documentserver_community/issues/88? In other words, does occ documentserver:flush produce output other than

Uncaught TypeError: Cannot read property 'b8d' of undefined

If so, we could set up dev environment, reproduce the bug and see if we can fix the Document Server Javascript.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nextcloud/documentserver_community/issues/100#issuecomment-620447169, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWGAGJ443TOJATNYFMR373RO2EQPANCNFSM4LT7KQHQ .

[davy39]

I had same kind of issue with saving into nextcloud. I think my issue was related to documentserver configuration. I guess I solved it by changing this option : "services": { "CoAuthoring": { "requestDefaults": {"rejectUnauthorized": false

[schniepp]

@davy39 : that sounds very interesting! Thank you so much for sharing! Where (how) did you change this setting? Are there any security implications? (Does this make unauthorized access to documents on the cloud more likely?)

[HFranz]

I had same kind of issue with saving into nextcloud. I think my issue was related to documentserver configuration. I guess I solved it by changing this option : "services": { "CoAuthoring": { "requestDefaults": {"rejectUnauthorized": false

As far as I see it, it skips the TLS certificate validation e. g. you use a self-signed certificate. I'm using a Let's Encrypt certificate. That would probably not help.

[Michael2222]

Hello @fthommen, why do you close this issue, if the bug not solved with standard nextcloud updates?

[fthommen]

Hi @Michael2222, this is a misreading :-): The "closed" refers to the mentioned NextCloud issue #20264, not this issue here (#100). I don't have the rights to close issues anyway :-)

[dedors]

I'm facing the same problem that changed don't get saved to NC. Running new installation 18.0.4 in docker.

Using occ documentserver:flush saves the document to NC.

[Michael2222]

Hello, I have tried

root@nextcloud:/var/www/html/cloud# sudo -u www-data php occ documentserver:flush

and this error occured:

In ConverterBinary.php line 64:
change_code: a?this.Nb.splice(d+1,this.Nb[0]-d):this.Nb[0]!==d+1&&0!==a&& this.Nb.splice(d+2,this.Nb[0]-d-1),this.Nb[0]=d+1)}0== =a&&this.Nb[0]!==d+1&&(this.Nb.splice(d+1,0,this.Nb.length-d-1),this.Nb[0]=d+1);c=1+this.Nb[0]+this.Nb[d+1]+2*a;this.Nb[c+0]=0;this.Nb[c+1]=0;return 0!==d||0!==a?this.Nb[c-1]:0}; b.prototype.saa=function(d,a,c,e){d=this.lxb(d,a);this.Nb[d+0]=c;this.Nb[d+1]=e};nb.prototype.qYb=function(d,a,c) this.Nb[this.lxb(d,a)+1]=c};nb.prototype.BG=function(){this.bb&&(this.bb.ey.b8d(),this.bb.k d.Z7a(Kl))};
  change: Uncaught TypeError: Cannot read property 'b8d' of undefined
  DoctRenderer:<result><error index="815" /></result>

documentserver:flush [--output [OUTPUT]]

and no update my file.

[timo12357]

@icewind1991 @rullzer @nickvergessen @blizzz What can we do to get this severe issue fixed and included in a Nextcloud release?

[Joe7new]

I completely agree with you ! I don't unterstand why such apps are offered as official with such a servere bug- should be declared as beta! I like NC, but would be better to have less apps that works stable. Less is sometimes more. Still hoping that it will be fixed- maybe in NC19 ? kind regards, Joe

[fthommen]

NC19 is out.Any idea, if this issue has been fixed there? It isn't mentioned in the release notes, though. In our environment one of the primary usages of NC is the collaborative editing of office documents. This bug severly hinders this functionality.

[thmo]

I still see the issue with NC19, using the OnlyOffice app 4.2.0, and both, documentserver_community 0.1.5 as well as external documentserver 5.5.3.39.

[MuellerSeb]

Does the 0.1.6 update affect this issue in any way?

[sbellm]

No, Issue with NC 18.0.6 is still here, no changes... :(

[richardrey]

Hi, I have the same problem, version 19.0.0 is deployed, cron service is executing correctly, but no changes from onlyoffice have effect in nextcloud, I can edit documents but the changes are not saved at any time, the changes, but I have noticed that when finished the edition of the document if I go to:

save a copy as

it lets me select the path where I want to save the document and it creates a new document with a different name but if it contains the changes, the problem is that I should be able to save the changes in a document but every time I want to make a change I have to Saving your changes is a new document, saving it as a copy.

Can someone know how to solve the problem is not that I cannot save that I cannot modify an existing document in nextcloud

this is the state of my installation.

[Joe7new]

Progress in syncing with onlyoffice !! Update to NC 19 , documentserver_community 0.1.7 (installed manually) and latest onlyoffice app and after a while the syncing is done ! That are good news! and the bad one (maybe just because of my configuration and only my problem?) : pictures inserted in the document are lost (I did an upgrade to php7.3-maybe that's the problem) . Is that a problem of my configuration ? (Ubuntu server 18.04).

But it gets moving ! regards, Joe

[dedors]

I updated the documentserver and edited a file 5 hours ago, it did not get saved.

[Joe7new]

tested right now again- after closing the document the sync happens within somes minutes ! I only (!?) have problem with documents with pictures in it - the pictures are lost even when Desktop syncing client is down. When I open the document in browser after some time- then the pictures aren't shown. Except that fact syncing onlyoffice docs with desktop client seems to work for me now - what are the experiences of other users ? regards, Joe

[richardrey]

I have updated everything but I still have the same error the document is not saved or I have tried plain text.