AssemblyFormatAsOrigin configuration issue

[kunkunj]

Why do I configure assemblyFormatAsOrigin to false and still crash the process when saving doc documents

[igwyd]

Hello @kunkunj, what behavior do you expect from this setting? Describe your case step by step and show error.

[Fantu]

Hi, I also had this issue on latest update tried previous year to version 8 and reverted to version 7.5.1.
assemblyFormatAsOrigin to false was a workaround to error on save (and lost of changes done in some files), it is a setting that was given to us by your support in the 2022 and reapplied any update done (we have the enterprise license), is it no longer necessary in the latest versions? Unfortunately I did not have enough time to do in-depth tests (on the day when I tried the update) and I did not want to risk losing changes like those I had years ago and so for the moment I restored the server from the backup with the old version.

[igwyd]

Hello @Fantu, since you have a license better contact tech support, I have no information about your case.

[Fantu]

Yes I will do it when I try the update again if it happens again, but it won't be a problem to do further tests, by now on that server they work every day and many with even over 40 people together and when I do the updates it's always in the evening, then I do some tests and if there's something wrong I have to restore from backup.
The problem however seems to be easily reproducible, I noticed it immediately after updating, setting that parameter to false and doing only quick tests of modifying some files in various formats (doc, docx, odt); I then closed the documents and seeing that it did not save (on nextcloud server) I checked the onlyoffice server and there were errors in the logs.
Could you also just do a quick check if with the latest version by setting that parameter to false you don't get any errors? Since it has happened to other users I don't want to risk wasting another evening (or more if I have to also redo every test that they tell me to do following the opening of a new ticket)

[igwyd]

I found this bug, it has been fixed in v8.1.0. I also checked that it does not repeat in v8.3.2. But I recommend you check it out in your environment to make sure.

[Fantu]

Big thanks for the reply, the "failed" upgrade was with 8.0.x (probably 8.0.1 but I'm not sure), so if that bug should be fixed in 8.1.0 and not reproducible in 8.3.2 I should have less risk of waste another evening.