Skip to content
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

Upgrade from 4.12.0~ynh2 to 5.2.1~ynh4 involve loss of data - empty spreedsheats #176

Open
b01xy opened this issue Mar 2, 2023 · 5 comments

Comments

@b01xy
Copy link

b01xy commented Mar 2, 2023

Hello,

We made the upgrade from 4.12 version to 5.2.1 version of cryptpad and some (all ?) users complained because when they tried to open their documents it proposed to them to update this document and the document ends empty.

I will try to restore an 4.12 versio on another server, but just to say be careful in case you do this update to have ways to roll it back in case it goes wrong

@Ddataa
Copy link
Member

Ddataa commented Mar 3, 2023

Hello @b01xy thanks for your help

if you do want to help and receive help, please start by filling up the issue template so we can move forward from users complained to some concrete logs and errors to work on...

we did has much testing as possible. And we try to get it tested by the community as well before release...PRs, tests and the dev branch that have been moving forward since last october in this same repository for everyone to participate too.

We did test the upgrade like this :

install a clean yunohost server on a VPS
install cryptpad version 4.12.0
verify it works, create an account and few documents
upgrade to new version 5.2.1
verify it works, access account and documents

the only things we can do is do that again and see if there is errors like you described...providing you have been following the administrator recommandations received by email throught the installation/upgrade process

@Ddataa
Copy link
Member

Ddataa commented Mar 3, 2023

we found an issue, it has been solved with the last updated version.

@b01xy
Copy link
Author

b01xy commented Mar 4, 2023

hello,
ok, thanks, but the last updated version didn't solved the problem for me neither, it made the things worse, I'll try to give some more documented input in this issue #181

@Ddataa
Copy link
Member

Ddataa commented Mar 5, 2023

have you tried the lastest version 5.2.1~ynh6 ?

@Ddataa
Copy link
Member

Ddataa commented Mar 25, 2023

@b01xy how is this issue doing ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants