-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Public page styles are broken on #3207
Comments
This is strange, because I was testing stuff yesterday for #3187 and everything was working fine! |
This comes from bde1150 |
Just reassured. I am on master, Chrome 55∞ macOS 10.11.6.
|
No, this is a easy one: // Do not initialise scss appdata until we have a fully installed instance
// Do not load scss for update, errors, installation or login page
if(\OC::$server->getSystemConfig()->getValue('installed', false)
&& !\OCP\Util::needUpgrade()
&& \OC_User::isLoggedIn()) {
$cssFiles = self::findStylesheetFiles(\OC_Util::$styles);
} else {
$cssFiles = self::findStylesheetFiles(\OC_Util::$styles, false);
} I didn't realised that public pages don't have a logged-in user! |
The problem seems to be here: why do you disable the SCSS for non-logged in users? The login page should also be done within SCSS. |
Is there a way to move CSS and SCSS into different namespaces? So that we know if it is CSS or SCSS - relying on some magic under the hood is always confusing and causes weird bugs as above. |
* checks if the user is on the login page or not instead of check if the user is logged in * fixes #3207 Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fix is in #3223 |
Separate issue -> moved to a new issue. |
I could reproduce @ChristophWurst find:
I looked into it and it seems there all stylesheets with the route
/css/core/
are missing (e.g styles.css) .There is definitely something wrong with the routing/embedding...
@skjnldsv @MorrisJobke
The text was updated successfully, but these errors were encountered: