3

Exact Duplicate:
Clicking on tags with wildcards gives you a blank page

I think since yesterday links in the interesting and ignored tags sections that include wildcards changed their behaviour to the following:

python* -> http://stackoverflow.com/questions/tagged/python*

That page obviously doesn't exist and I'm getting a blank page. Wouldn't the original behaviour that linked to: http://stackoverflow.com/questions/tagged/python be more useful?

Edit: after reading this answer and following re-adding advice, I can confirm that re-adding works until page is reloaded. So it clearly is a bug.

Edit2: this is not a duplicate of Searching for a tag containing * breaks. I'm not searching for anything. These are links in interesting/ignored tags sections! And the change has happened sometimes yesterday. The previous questions have to do with completely different issues. Please open this question.

Edit3: this is not a duplicate many times over. The

python* linked to http://stackoverflow.com/questions/tagged/python

now it links to: http://stackoverflow.com/questions/tagged/python*

How is it a duplicate?

here is the except form Kyle's answer:

When you click on a wildcard tag, it does not (and never has) taken you to a list of questions with tags that match that wildcard.

(highlighting mine). Yes, Kyle, it never has taken you to a list of question that match that wildcard. But it has taken you to the one single tag (python in this case). What is it if not a regression in usability is beyond me.

marked as duplicate by Kyle Cronin Jul 17 '09 at 13:40

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • I expanded the duplicate section to include 4 links. Did you review them? I'm pretty sure you'll find your exact problem in more than one of them. – Kyle Cronin Jul 17 '09 at 14:23
  • question that were closed as duplicates but aren't. – SilentGhost Jul 17 '09 at 14:25
  • I do accept that slightly different triggers have caused the same error, so I've opened back up meta.stackexchange.com/questions/6441/… which really is an exact duplicate of this question – Kyle Cronin Jul 17 '09 at 14:38
  • thanks for that. I'd appreciate if that question were tagged properly. – SilentGhost Jul 17 '09 at 14:47

Browse other questions tagged .