It's here, the new, improved, latest whine-free episode of Eat This Podcast:
How much does a nutritious diet cost? [eatthispodcast.com] Depends what you mean by "nutritious"
It's here, the new, improved, latest whine-free episode of Eat This Podcast:
How much does a nutritious diet cost? [eatthispodcast.com] Depends what you mean by "nutritious"
@kdfrawg It wasn't the CSS that got me, it was the cache. And that's been a problem before. It is because I don't do it very often that a checklist would help.
// @c
@kdfrawg Nah. It's just the baby boomer bulge tapering off. Or rather,tapering on.
// @indigo @jenso
@kdfrawg Makes me think I really ought to have a proper. Written checklist for when I try to do stuff like that.
// @c
@ukhaiku Now, what was the name of that place we always stay at? Hang on a sec. Time to ransack the outboard memory. BRB.
@c I'd like to remove my head, if you can arrange that. Or at least de-gauss it.
@c Would you like to know what a shitshow of a soi-disant web guy I am?
The fucking cloudflare cache was on on the live site. Get rid of that, and the simple address {display: none;}
works perfectly.
<slinks off to beat brains out against a brick wall>
@c Amazingly, this works:
#primary .post .entry-meta address { display: none; }
But I have always thought that CSS selectors work at the lowest level. That is, I reckon the above targets address
in a div in a div in an ID.
But then, why would address
is on its own not target all instances?
@c Nope, that isn't hitting it either.
I think I had better go back to testing locally.