You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: NC25 not working with disabled Theming app #34338
Since the theming app now also hosts the accessibility settings, should we force enable it?
Feels weird that an admin can decide to punish people for their accessibility lacks by disabling an app they just don't need themselves?
Hey @szaimen, the theming app is disabled by default in the snap because it adds warnings about not having imagick. Did you ever test updates when this app is disabled? Any bad side effects? Has anyone considered splitting critical functionality out of a non-critical theming app so folks who don't want imagick installed don't constantly see a warning?
it's not a warning as it's not yellow and not an error as it's not red. It's an info.
The problem is when there are no errors/warnings the headlines still say "Setup warnings", so that's why you might confuse it for that.
The reason is it was merged with the accessibility features as they shared to many settings and technics and need to work hand-in-hand, but Accessibility is not optional, it's one of the core principals of the Nextcloud project, see https://nextcloud.com/about/ (middle of the page, seems to miss anchors at the moment).
So please remove any code that would try to disable/remove/prevent theming.
it's not a warning as it's not yellow and not an error as it's not red. It's an info.
The problem is when there are no errors/warnings the headlines still say "Setup warnings", so that's why you might confuse it for that.
That's a bit pedantic. The people who log bugs about that don't see it that way. Fixing that messaging would be helpful.
So please remove any code that would try to disable/remove/prevent theming.
That's just signing us up for triaging more invalid bug reports. Can we please consider moving accessibility to another trimmed down app specifically for it?
Due to the theming app being forcibly enabled, as of 25,
we're running into problems when using our own customized theme which required the theming app to be disabled.
Our customized theme redefines some css-vars and styles , these are now being overwritten by the theming app.
Do I understand correctly that the reason for the forcibly enabled theming app is the need for "accessibility features" ?
Due to the theming app being forcibly enabled, as of 25, we're running into problems when using our own customized theme which required the theming app to be disabled. Our customized theme redefines some css-vars and styles , these are now being overwritten by the theming app.
Do I understand correctly that the reason for the forcibly enabled theming app is the need for "accessibility features" ?
@tonyguepin similar situation here. I was trying to use just one instance of NC 27 for multiple domain names, and depending on the domain show a different theme. I spent quite a lot in reading posts and docs, and it seemed feasible as some of the configs worked, while others not
So I kindly ask: now that is not possible to disable theming, how to override/inject CSS properties into custom themes ("themes" folder, using the "example" theme/folder as template for others) now that functions in defaults.php like
public function getScssVariables() {
return [
'color-primary' => '#745bca'
];
}
are ignored or simply overridden by the theming functionality?
Activity
genma commentedon Oct 5, 2022
I've the same issuses a written a blog post in French with some screenshot https://blog.genma.fr/?Nextcloud-25-l-application-theming-casse-l-affichage-des-CSS
AndyScherzinger commentedon Oct 6, 2022
Looping in @PVince81 and @juliushaertl
PVince81 commentedon Oct 10, 2022
and @Pytal
Pytal commentedon Oct 12, 2022
Some dashboard js depends on theming to adjust the header
Tracking in #33969
nickvergessen commentedon Oct 14, 2022
Since the theming app now also hosts the accessibility settings, should we force enable it?
Feels weird that an admin can decide to punish people for their accessibility lacks by disabling an app they just don't need themselves?
szaimen commentedon Oct 14, 2022
WIP here: #34609 however I didn't test yet what happens if you disable the app and upgrade to this branch.
kyrofa commentedon Apr 30, 2023
Hey @szaimen, the theming app is disabled by default in the snap because it adds warnings about not having imagick. Did you ever test updates when this app is disabled? Any bad side effects? Has anyone considered splitting critical functionality out of a non-critical theming app so folks who don't want imagick installed don't constantly see a warning?
nickvergessen commentedon Apr 30, 2023
it's not a warning as it's not yellow and not an error as it's not red. It's an info.
The problem is when there are no errors/warnings the headlines still say "Setup warnings", so that's why you might confuse it for that.
Also note, since Nextcloud 25 the Theming app is one of the apps that must always be enabled:
https://github.com/nextcloud/server/blob/stable25/core/shipped.json#L100
https://github.com/nextcloud/server/blob/stable26/core/shipped.json#L100
https://github.com/nextcloud/server/blob/master/core/shipped.json#L100
The reason is it was merged with the accessibility features as they shared to many settings and technics and need to work hand-in-hand, but Accessibility is not optional, it's one of the core principals of the Nextcloud project, see https://nextcloud.com/about/ (middle of the page, seems to miss anchors at the moment).
So please remove any code that would try to disable/remove/prevent theming.
kyrofa commentedon May 1, 2023
That's a bit pedantic. The people who log bugs about that don't see it that way. Fixing that messaging would be helpful.
That's just signing us up for triaging more invalid bug reports. Can we please consider moving accessibility to another trimmed down app specifically for it?
szaimen commentedon May 1, 2023
I think the best way forward would be this: #36607
tonyguepin commentedon Jul 1, 2023
Due to the theming app being forcibly enabled, as of 25,
we're running into problems when using our own customized theme which required the theming app to be disabled.
Our customized theme redefines some css-vars and styles , these are now being overwritten by the theming app.
Do I understand correctly that the reason for the forcibly enabled theming app is the need for "accessibility features" ?
gioman commentedon Jul 29, 2023
@tonyguepin similar situation here. I was trying to use just one instance of NC 27 for multiple domain names, and depending on the domain show a different theme. I spent quite a lot in reading posts and docs, and it seemed feasible as some of the configs worked, while others not
i.e.
https://help.nextcloud.com/t/howto-individual-themes-per-domain/27585
the part that isn't working is the override/injection of some CSS property, as described in this legacy page of the docs
https://docs.nextcloud.com/server/12/developer_manual/core/theming.html
and finally/sadly read this post
https://help.nextcloud.com/t/howto-individual-themes-per-domain/27585/24
So I kindly ask: now that is not possible to disable theming, how to override/inject CSS properties into custom themes ("themes" folder, using the "example" theme/folder as template for others) now that functions in defaults.php like
are ignored or simply overridden by the theming functionality?
Thanks in advance