[Bug]: Collectives asks which file should be saved whenever a change is made

[Goemann]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I create a new page in Collectives 3.4.0, edit it, and the next time I edit it, I always get the following message: The file was overwritten. Your current changes cannot be auto-saved. Please choose how to proceed.

Steps to reproduce

1. Create a new page in Collectives 3.4.0
2. Click on Done
3. Click on Edit
4. Message "The file was overwritten. Your current changes cannot be auto-saved. Please choose how to proceed." appears

Expected behavior

I don't have to choose between two versions.

Nextcloud Server version

31

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

Hetzner StorageShare

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

[mejo-]

Thanks for the report @Goemann. Which Nextcloud server version do you use? Also, are you the only user of the Collective? And do you use the Nextcloud file sync client to synchronize your data to your local device?

[Goemann]

Thanks for the reply @mejo-
Nextcloud Server version: 31.0.10
No, multiple users access the collectives.
No, I don't synchronize the files with my computer.

[mejo-]

Nextcloud Server version: 31.0.10

If I remember correctly, there were recent fixes related to the problem you describe. Could you upgrade to 31.0.13 after it got released later today and see whether this fixes the problem for you?

[Goemann]

Thanks again. In this case, we will have to wait until Hetzner distributes the version, as we do not have root access to the server ourselves.