Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Related Question:
Searching for a tag containing * breaks

I have tags in my "Interesting Tags" with wildcards, like html*, php* and so on. If I click on it it goes to*, and all I get is a blank page. It used to be that clicking on them would take me to the page with questions tagged just php. What happened?

share|improve this question
There's an issue with ASP.NET MVC and asterisks in the titles. Nevertheless, this is a dupe:… – Kyle Cronin Jul 17 '09 at 4:34
Ah, I didn't see that other one. Sorry. Jeff says in that post that this was never supported, but it used to "degrade gracefully" such that clicking on a tag with wildcards actually took you to the tag page minus any wildcards. It's not behaving that way anymore, which I'd consider a bug. – Paolo Bergantino Jul 17 '09 at 4:37
I suspect that it may not be (easily) possible to degrade gracefully if the URL contains an asterisk, but it would certainly be possible to make sure that a tag link doesn't contain an asterisk. – Kyle Cronin Jul 17 '09 at 4:44
This isn't an exact duplicate. I realize they are very closely related, but the other question is complaining about being unable to search for it, I never attempted such a thing. It has always been the case that simply clicking on a tag with wildcards behaved a certain way, and it stopped doing this very recently. This is a bug. – Paolo Bergantino Jul 17 '09 at 5:56
They're both symptoms of the same problem. It's not whether you clicked on a wildcard tag or searched for a wildcard tag, it's that you included an asterisk in the URL that causes the blank page. – Kyle Cronin Jul 17 '09 at 6:23
Apparently this is a very recent change where clicking on wildcard tags brings up a blank page, so I'll reopen. (hopefully this will be good enough for…) – Kyle Cronin Jul 17 '09 at 14:40
yes, it's good enough. Could you please tag it properly (or at least copy tags from my question). Apparently, auto suggestions are not that great. – SilentGhost Jul 17 '09 at 14:46

We now replace the client wildcard (*) with the server wildcard (~) on tags.

However, be careful, because the server has rules that the client does not. Most notably, any wildcard searches MUST be a minimum of 4 characters in length (not including the wildcard chars themselves), or they are ignored.

share|improve this answer
So that's why geo* doesn't bring back all the results for geospatial and geolocation as well :( – Rowland Shaw Feb 16 '10 at 13:55

You must log in to answer this question.

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