Wedge

No, but mostly because there's simply no sane way to handle that permission in a UI that is designed to be constrained inside the confines of a simple settings page.Mostly because it's actually buggy. The permission is defined in the permissions as an own/any pair (and that relates to my comments above) but it's used in active_members_action as a simple permission, as allowedTo('view_active_members')

It needs to be one or the other.

Yup. The 403 is because fatal_lang_error always pushes out HTTP 403 by default, though you can override that to whatever error code you like.

Davros was right - the Doctor... the man who runs, who never looks back because he daren't - out of shame. No, he wouldn't go back to tell Brian what happened. He'll just move on and take that guilt with him, like he does every time. This is not the first time he has had to abandon his companions to their fate.

Even in New Who, he had to leave Donna to her fate, forgetting him. But look back at Old Who, you have Adric[1], Peri[2], Jamie and Zoe[3], Sarah Jane[4]... the list goes on, but it's not always them leaving because they want to, or he wants them to, but because circumstances forces him to leave them behind in some fashion.

That's incidentally one of the things that is objected to - how does the Doctor know his companions will be safe? The answer is, ultimately he doesn't.

1.	Dead. Not really missed.
2.	She was left with King Yrcanos (Brian Blessed, no less, looking like he'd just stepped off the set of Flash Gordon), with her thought to be dead for several episodes of Trial of a Time Lord.
3.	After the Time Lords caught up with the Doctor back in his second incarnation, they forced a regeneration, sent these two home with no memory of the Doctor and largely exiled him on Earth.
4.	She was left behind, hundreds of miles from home, because the Doctor had to return home to Gallifrey.

At the end of the last episode.

The ability to push features into plugins is one of the reasons I wanted to make sure there was a battle-hardened plugin system there ;)

Writing them isn't hard, once you get into the mindset. The mindset simply is: I can run my own code at *these* places, if I were inserting my own code there to do a job, what would I write? The rest is pure packaging.

Well, why isn't nobbc handled in preparsecode? It's supposed to be.

I don't blame him from shying away from plugins. If you've never had to think in that mindset before, it takes some getting used to. Fortunately I'd come from SMF where I'd already been making lots and lots of use out of it.[1]

But building is less a skill and more an art in doing the dance the right way, especially if you're used to just adding code wherever you feel like.

1.	I'm not going to claim that I made *best* use of hooks, I think Dime probably has that title. But I certainly made noise about making use of them whenever possible.

Both are processed separately, interesting. But more importantly, nobbc should be converting them on preparse to not be parseable tags in the first place, strpos or otherwise.