5

OK, so after discussions in chat about the future of , I created a tag synonym the wrong way, from <-- . Realising I made the wrong one, I went to the mod tools and hit "swap". Everything reflected correctly in the Tag Synonyms console, so I merged the two tags together.

Now, everything seems broken. redirects to , which is empty and doesn't exist, and is showing 0 questions (correctly).

Official SE team: Halp please!

enter image description here

enter image description here

1
  • 1
    It's SBS, isn't it broken by definition?
    – voretaq7 Mod
    Commented Aug 30, 2012 at 15:09

1 Answer 1

Reset to default
3

I'm pretty sure it's not broke. It doesn't redirect in my browser, nor in the alternate I just tested (which has never been to that tag's page before). I think your browser has the redirect cached and isn't actually checking with SF's servers.

8
  • No dice, just tried it in IE (which should on its own indicate that it has a completely empty cache and browser history) and I'm still seeing the bad redirect
    – Mark Henderson Mod
    Commented Aug 30, 2012 at 0:44
  • Also just tried on the iPhone and iPad, both of which have never been to that particular tag before
    – Mark Henderson Mod
    Commented Aug 30, 2012 at 0:45
  • I just tried it on two different servers with Lynx, no redirect... I'll try my phone.
    – Chris S Mod
    Commented Aug 30, 2012 at 0:48
  • Just tried from my Android, still no redirect. Network proxy?
    – Chris S Mod
    Commented Aug 30, 2012 at 0:50
  • Yes... it could be a caching proxy on our network...
    – Mark Henderson Mod
    Commented Aug 30, 2012 at 0:57
  • Nope, it's not our network cache
    – Mark Henderson Mod
    Commented Aug 30, 2012 at 1:09
  • 1
    Unofficial update: Something somewhere was cached. General consensus in chat was it could have been something cached at Stack Exchange, as it was unreliably reproduced by different people. After nearly 2 hours everything has corrected itself.
    – Mark Henderson Mod
    Commented Aug 30, 2012 at 2:05
  • I've had similar issues at home and the problem turned out to be the cache on my firewall/proxy, which is so easy to overlook.
    – John Gardeniers
    Commented Aug 30, 2012 at 9:51

You must log in to answer this question.

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