@baris seems to work now 👍
Can't set up NodeBB from branch that's not master
crawls out of bed
groggily reads post
Oh, the buster problem. Usually the issue I found was a misplaced
;that messed up the code to the point that the buster wouldn't bust. I say usually because it's been a few different problems for me that has caused the buster not to bust in the past, and I've been able to solve it a couple of different ways:
- check and see if there are any misplaced colons or semicolons, or any misplacements in the CSS at all
- revert to a previous version and make the changes you did after that
- wave your wand three times and say the magic words, then restart your NodeBB and check again
Let me know if any of these work, especially the third option because I think it's the best.
@Tanner, there's no custom CSS, so it seems to be something from 0.5.1 of NodeBB.
Also, I'm gonna try my hand at a plugin you requested. We'll see how it works out.
@Ted It could still be a mixup in the CSS either way, even if there's no custom work or not. Could be a plugin, could be the theme, but that's been the major cause of my problems to date.
@Tanner, tee total fresh install, with no plugins. Must be something with the theme then.
I'll scan through in a bit and see if I can spot the issue. Since you've sounded off here, I'm going to try to do the same for you.
@Ted I'll also see if I can reproduce the issue with a fresh install and let you know what I come up with in terms of a solution.
So I looked through the recent commits to the 0.5.1 lavender theme and couldn't find a wayward colon, semi or not.
Is anyone else having this issue? If not, I'll just try again from the snapshot before NodeBB.
Our local dev environments are fine (although I do switch back and forth between
0.5.1)... Let me start from scratch later today and see.
@julian, I think I fixed this issue. I rolled back to a snapshot before I installed NodeBB and re-cloned the 0.5.1 branch and it installed without an issue and I have sweet, glorious CSS!