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

Weird behaviour for logged in users in maintenance mode #15418

Closed
jvillafanez opened this issue Apr 6, 2015 · 8 comments
Closed

Weird behaviour for logged in users in maintenance mode #15418

jvillafanez opened this issue Apr 6, 2015 · 8 comments
Milestone

Comments

@jvillafanez
Copy link
Member

Steps to reproduce

  1. Log in with an user
  2. From the OC command line, set the maintenance mode (sudo -u www-data ./occ maintenance:mode --on)
  3. Do some ajax stuff with the logged in user (for example, in the files view, try to get the contents of a folder)

Expected behaviour

You are kicked to the maintenance screen

Actual behaviour

You stay in the page getting errors. For example, if you try to get the contents of the folder, you stay in the current folder instead of changing it; if you want to know the file shared with you, you'll see that there are no files shared with you even though it's wrong.

This behaviour stays until the user loads another page, then the user is redirected to the maintenance screen

Server configuration

Operating system: ubuntu 14.04

Web server: apache 2.4.7

Database: mysql

PHP version: 5.5.4

ownCloud version: 8.0.3RC1

Updated from an older ownCloud or fresh install: fresh install

Browser: firefox

@nickvergessen
Copy link
Contributor

pretty much the same problem like when LDAP and others are not there.
We need a wrapper in the get(), post(), ... methods in js to catch these cases and redirect.

@nickvergessen
Copy link
Contributor

cc @MorrisJobke can you find the ldap exception issue for a cross link quickly?

@MorrisJobke
Copy link
Contributor

@nickvergessen #15332 or #15357 ?

@nickvergessen
Copy link
Contributor

The later one is what I was looking for

@nickvergessen nickvergessen added this to the 8.2-next milestone Apr 7, 2015
@PVince81
Copy link
Contributor

PVince81 commented Apr 7, 2015

This one is tricky. Every app needs to fix their ajax calls to be able to react properly on 503 http codes and automatically show a proper error message or redirect accordingly.

@jvillafanez
Copy link
Member Author

Checked also with single-user mode: same behaviour with normal users

@ghost ghost modified the milestones: 9.0-next, 8.2-current Sep 21, 2015
@ghost ghost modified the milestones: 9.1-next, 9.0-current Feb 20, 2016
@ghost ghost added the old-inactive label Feb 20, 2016
@PVince81 PVince81 modified the milestones: 9.1-current, 9.2-next Jun 14, 2016
@PVince81
Copy link
Contributor

in recent versions, a notification will appear that an error occurred and the page will reload, which will redirect to the login page (or maintenance page followed up by login page when it comes back)

@lock
Copy link

lock bot commented Aug 3, 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 3, 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

5 participants