Wow, that took me a good while to figure out. I don't use tags myself, and it turns out there is a glitch in the software added from a recent update that I hadn't noticed and no one had reported. :(
Fortunately there's an easy fix:
Go to engine.php and comment out line 357 so it looks like this:
// if ($args['text'] != '') $value = BOLTMtexttools(array('', $args['text'], $value));
At some point I added a way to integrate text formatting features directly into the function output, but the text= parameter is also part of the tagging system, so you have the conflict right there.
A better way to fix it would be to change the format of the tag command from
[(query page=index.tags text=whatever fmt='[[{+p}]]')] to [(query page=index.tags tag=whatever fmt='[[{+p}]]')]
But that would be a bit more complicated, so I'll put that on my to do list to figure out how to do this optimally. And hopefully without breaking sites.
Actually, thinking out loud, if you want to retain the text formatting capabilities, you could for now replace line 357 with these four lines:
if ($args['text'] != '') {
$value2 = BOLTMtexttools(array('', $args['text'], $value));
if ($value2 != '') return $value2;
}
That actually seems to fully solve the conflict. And using a tag= parameter may not be the best approach anyway as text= is used for regular text based searches that don't involve tagging.
Anyway, let me know if this doesn't solve the problem for you. I probably won't do a release for this small fix as I'm working on a bigger release for the near future, but will be sure to include some fix when I do. And it won't hurt to think about this a bit more to make sure we get it fixed right...
Thanks for reporting this! I was actually thinking about adding tag capabilities to my own site sometime soon. Should be easier now that it is working!
Cheers,
Dan