See earlier bug for description of symptoms and background: How did the [html+php] tag come to exist and how can we make it die?.

This question created the tag android+sqlite+insert. Please do not edit the question just yet, lest you destroy evidence. Yes, it needs improvement and could possibly need closing as Too Localized, but let's not worry about that right now.

You will note that the user has one rep. One rep.

How did this user without the ability to create tags not just create a tag, but create a bogus tag?

closed as off-topic by Undo, Martijn Pieters, ChrisF, Aza, mhlester May 9 '14 at 20:50

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Undo, Martijn Pieters, ChrisF, Aza, mhlester
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    here's the evidence just in case: i.stack.imgur.com/XnlGK.png – ben is uǝq backwards Mar 13 '13 at 7:03
  • 1
    While clicking on edit link, it shows three different tags, strange !!! – Raynold Mar 13 '13 at 7:03
  • Is there, perhaps, a way to start a new question by giving querystring parameters to a page that in some way includes tags? Spaces in querystrings are, famously, represented by plusses. Also, clicking on the tag itself doesn't lead to a tag-wiki - but a search with all three tags included. – J. Steen Mar 13 '13 at 7:17
  • 1
    this means the bug is not fixed – BЈовић Mar 13 '13 at 8:05
  • 3
    what you say is true; that did indeed happen, and the tag is credited to the 1-rep user; investigating; edit: ah, I see... – Marc Gravell Mar 13 '13 at 10:59

Thanks for reporting; it looks like we had some tag-handling code that processes both url forms (where + might be used interchangeably with %20 as a separator) and "text" forms (where we only expect space as a separator) - so some wrong code paths were taken when validating the tags. This will be fixed in the next build.

Basically, , and already existed, and it got a bit confused.

Not the answer you're looking for? Browse other questions tagged .