-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
pretty much the same problem like when LDAP and others are not there. |
cc @MorrisJobke can you find the ldap exception issue for a cross link quickly? |
@nickvergessen #15332 or #15357 ? |
The later one is what I was looking for |
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. |
Checked also with single-user mode: same behaviour with normal users |
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) |
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. |
Steps to reproduce
sudo -u www-data ./occ maintenance:mode --on
)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
The text was updated successfully, but these errors were encountered: