Hey John - Thanks for the tip. I've considered that too, but on a
production system I guess that's not the best tack, which brings me to what
I might consider the final answer ... I shouldn't be making CSS updates on a
production system anyway, right? Right.
The edge-case in this scenario was
I've got a couple of Radiant instances out in the wild that I want to
smoosh into a single instance with spanner's multi-site-extension. I'm
also wanted to upgrade to 0.9.1 at the same time, so I've decided it'd
be easiest to start a fresh with a clean install. I'll worry about
content later.
I'm hoping to do a quick blog post and wiki page about this this week.
But if all you need to do is hide some things and you are on 0.9, then edit
overrides.css. It's the last stylesheet loaded and it won't be touched by
updates.
But the new CSS won't be generated if the already-generated file
On Jul 20, 2010, at 9:26 PM, Andrew Reid wrote:
On 21 July 2010 10:22, Andrew Reid andrew.r...@synergetix.com.au wrote:
What am I not doing right here? Do I need to do something else to
restrict the visibility to (and access to) that tab?
A bit more digging[1] and fiddling later and I've