documentserver_community icon indicating copy to clipboard operation
documentserver_community copied to clipboard

No real coediting

Open Sicoval31 opened this issue 1 year ago • 9 comments

Nextcloud 25.0.7 (snap auto upgrade) office nextcloud 7.8.0 Community document server 0.1.13

since few months, when editing a file (docx, xlsx) with OO and many partners, the collaborate editing mode doesn't work fine : Partner A add info in a Excel cell, partner B show wich cell, but never see what is added, even if Partner A save the file.

Need to quit OO and reload the file. try with Firefox, edge or chrome .. same problem try with other computer : same problem

No error message

It's not a collaborate mode

Thanks to repair or explain why coediting is not allow

Sicoval31 avatar Jul 18 '23 07:07 Sicoval31

This seems to be a duplicate of #288 . [QUOTE:] "Cursor of co-editors is displayed but changes aren't visible"

zeptomoon avatar Jul 20 '23 07:07 zeptomoon

Nextcloud 27.0.2, Community document server 0.1.13

We face the same issue since the update to 27.0.2. It worked fine in NC 26 we had before. Users must quit and enter OnlyOffice to see work of others.

And yes #288 refers to the same problem, but this issuer also refers here.

mattiscb avatar Aug 24 '23 08:08 mattiscb

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 60 days. Thank you for your contribution!

Retaking repo management include inheritance of old, not treated, and probablty obsolete issues, this is why it was decided to mark issues as stale.

github-actions[bot] avatar Feb 19 '24 00:02 github-actions[bot]

Any news to solve this problem ?

Sicoval31 avatar Feb 19 '24 06:02 Sicoval31

Did you try the last documentserver_community version released few weeks ago?

chadek avatar Feb 20 '24 21:02 chadek

Yes, installing the last 0.1.15 version. No change

Sicoval31 avatar Feb 21 '24 07:02 Sicoval31

Fixed in v0.1.16

chadek avatar Apr 07 '24 11:04 chadek

Don't work. Same problem Why closing directly whitout users testing ????

Sicoval31 avatar Apr 08 '24 06:04 Sicoval31

Right, sorry, I was trying to close duplicates of this issue that v0.1.16 aim to fix and this is clearly an other issue.

chadek avatar Apr 08 '24 09:04 chadek