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

Bogus downgrade error message related to browser session #24793

Closed
APTX opened this issue May 23, 2016 · 4 comments
Closed

Bogus downgrade error message related to browser session #24793

APTX opened this issue May 23, 2016 · 4 comments

Comments

@APTX
Copy link

APTX commented May 23, 2016

ownCloud stores a version in a user session which can lead to an error similar to:

Downgrading is not supported and is likely to cause unpredictable issues (from 9.0.2.2 to 9.0.1.3)

I'm not really sure how I got ownCloud in such a state but clearing ownCloud cookies resolved the issue. While I was getting this error in one browser ownCloud continued to work in other browsers.

A probable cause of this issue was discovered on IRC:

APTX: https://github.com/owncloud/core/blob/master/lib/private/legacy/util.php#L367
APTX: https://github.com/owncloud/core/blob/master/lib/private/legacy/util.php#L1419
so what happens is that they use the version from the current session
your cookie is used to open a specific session
which might still include the old one
using the version from the session is probably not a good idea

@nickvergessen
Copy link
Contributor

Well downgrading is not supported 🙊
When your session has a higher version then what you now have locally, you did one.

Sure the message is odd, but sounds like low priority to me.

@APTX
Copy link
Author

APTX commented May 24, 2016

I did not downgrade anything. No files were changed since the upgrade to 9.0.2 (last modified date matches). version.php contains:

$OC_Version = array(9,0,2,2);
$OC_VersionString = '9.0.2';

As I mentioned I only got the error in one browser. I don't know how the session got the way it did on that one browser. In the other browsers I could run the integrity check and it passed.

@PVince81 PVince81 modified the milestone: backlog Oct 14, 2016
@PVince81
Copy link
Contributor

Won't fix unless someone volunteers to spend the time to debug this corner case.

@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants