Thread:Imamadmad/@comment-26235098-20150711023302/@comment-4189499-20150711071055

Catinthedark wrote: Alright then. :) I did notice it on a few of your posts, too, your blog and also the board when you were changing terms in the poll pages. I've run into it with a category suggestion too though. It's on the general discussion board and so far only DCG has found it. :O I still haven't figured out how others find each other's blog posts, either. I discovered Primetime's on sugar drops only last night! :O And she only posted it back then, because she hadn't "discovered" my thread - which had been highlighted! :O So things do seem rather a bit random.

I looked at your module... no edits. Wow so you are one of those genius one shot coders, eh? I know it's simple but I always end up missing a semicolon or other equally stupid thing, and this after years of ... oops shhhh. ;) What about something less quirky though, maybe just unDab? or stripDab, or dabRemove? Granted, a touch of 'quirky' can be fun. ;) I would though apply the default behavior to arg1 nil or empty, as well as the literal case you've handled. The way most people find blogs is via Blog:Recent posts, which is linked under the "Community" link under the "Contents" tab of the navbar at the top of all pages. Ok, it's a little hidden, so I can understand it not being easy to find, but there was nowhere else to put it because of the sheer quantity of levels requiring too much space on the navbar that we had to scrap the dedicated community tab. Well, once you find it it's a great place to see all blogs people have posted!

I only managed to post that module in one edit because of that lovely console. Thanks so much for the links to how to get it to work. Normally I'd be making about a hundred edits just trying to find where That One Bug is that is messing the whole thing up!

I'll rename the template to UnDab for the sake of clarity (all pages automatically start with a capital letter unfortunately) but I'll leave DabBgone as a redirect for my own use :P

Since the module will primarily be used from inside the template, due to the fact there's just that much less typing to invoke it, I can't see much of a point getting it to recognise anything other than as "empty", but just in case I'll get it to recognise both the empty string and Nil as "empty" too.