Updating Discourse causes white on white categories

(Jake Jackson) #1


After the latest update (Beta 6) the category background on the home page is now a little stripe. However this UX change in conjunction with using a white category foreground colour makes the text unreadable.

Previously when the background color was behind the text this looked perfectly fine.

Is there custom CSS I can add to make the category background color show behind the text? I would rather not change the text color to black as the contrasting colors are harder to read on the individual category pages where the background image is still behind the text.

(Sam Saffron) #2

Can you try restarting?

(Jake Jackson) #3

Thanks Sam. A restart did the trick.

(Clay Heaton) #4

For what it’s worth, I had the same problem and restarting also fixed it.

(Sam Saffron) #5

yeah, its super annoying, something is not restarting right wrt docker manager

(Jeff Atwood) #6

This is an updater bug not a bug with the code per se.

(Sam Saffron) #7

I will try to get this sorted for our next point release it is quite bad.

(Zachary Lewis) #8

@sam I’m encountering this same issue. I’m running my docker install on Digital Ocean. What’s the safest/best way to properly restart Discourse?

(Zack) #9

You can also toggle the bar / box setting from bar to box back to bar and it’ll display the category names correctly.

(Sam Saffron) #10

reboot is fine ./launcher restart app is fine

(axil) #11

That did the trick without restarting thanks.

(Robin Ward) #12

Maybe we should add a restart button to docker manager?

(Sam Saffron) #13

Yeah I really want that. The odd thing is that it restarted but somehow data is old.

(Crackmacs) #14

where is this found?

Edit: Found it. Admin / settings / basic setup.

Corrected the white on white for me too :slight_smile: thanks!

(Jeff Atwood) #15

This is a blocker for the 1.2 release so let’s make sure we get it sorted next week @sam

(Sam Saffron) #16

This subtle and very complicated bug is now fixed via:


A sequence of events was causing incorrect json to be cached, we noticed this issue elsewhere in our infrastructure regularly but never managed to pin it.

(Sam Saffron) #17