Uh oh!
There was an error while loading. Please reload this page.
[stable20] Fix dashboard rendering if accessibility app is disabled - #23192
Conversation
rullzer
commented
Oct 5, 2020
/compile amend / |
Signed-off-by: Julius Härtl <jus@bitgrid.net> Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
a93558f to
2070ef6Comparemadmax2012
commented
Oct 31, 2020
For me the dashboard has still not been rendering properly after upgrading to 20.0.1. |
BloodyIron
commented
Nov 5, 2020
Yeah I just upgraded to v20.0.1 and the dashboard is broken the same still. This was the very reason I upgraded :/ |
jancborchardt
commented
Nov 16, 2020
@madmax2012@BloodyIron is it the same issue as #23163 ? If so please comment with further logs and info there so we can reopen, otherwise open a new issue with the relevant error / console logs. Thanks! :) |
monolied
commented
Nov 25, 2020
I have the same issue after updating from 19.0.3 to 20.0.2. The dashboard is entirely white with my avatar picture in the top right the only visible item and exception. The avatar is usable and, while invisible, the app icons are present, complete and usable, too. Also invisible, but usable, is the Nextcloud icon in the top left. The complete area below these shows no sign of hidden usability. During a reload, nothing pops up in nextcloud.log. Web server is nginx, OS is Debian 10.6 fully upgraded. Dashboard is listed as version 7.0.0. ( |
juliusknorr
commented
Nov 25, 2020
Could you check if it continues to be an issue after clearing your browser cache? |
monolied
commented
Nov 26, 2020
Yes, still an issue. I also tried several browsers and computers. Kinda surprised that not everyone seems to be able to easily reproduce it, actually, since it seems so robust and reliable. |
juliusknorr
commented
Nov 26, 2020
Please check if there is an error in the browser console and if it is actually the same or a different one as in #23163 (comment) |
monolied
commented
Dec 4, 2020
From the description I'd say it is the same error. However, I seem to have a different error message in the console (and it looks rather tellltale): |
backport of #23179