Q&A Performance Improvements
-
This post is deleted! -
Yes, the same thing happens for both replies and responses.
-
Same thing is happening for me too. I'm on Chrome on a PC.
-
This post is deleted! -
Good news! It is working properly for me now.
I thought it was still broken, but this time, clearing my cache and cookies did the trick.
Good job guys!
-
From the last 30 days seems reasonable to me, but my bigger issue is with the name of that tab.
"Featured" is definitely a totally different connotation than "Unanswered". If I'm clicking on a "Featured" tab, I'm expecting something about these questions to be unusual - they're especially tricky, or especially useful, or especially contentious. Just "not having been answered" doesn't fit the idea of "Feature" in my mind. Not enough difference between the word Featured and Hot in my mind.
No catchy one-word label is immediately coming to mind, but if I think of something, I'll post it.
Paul
-
I spoke too soon.
If I clear my cache and cookies then it works just fine. However, the next time I come to the site the problem is there again (new page whenever I respond or reply, plus I can't thumb anyone up). I have to clear my cache and cookies and login again in order for it to work properly again.
-
This post is deleted! -
This post is deleted! -
So sorry that I couldn't send the screenshots yesterday. I am swamped with work. I will try to get them to you later today. Hopefully really soon. It's weird because, now, as I type this it is working fine. Yet other times it doesn't. I'll document a few attempts and send it to you as soon as I can.
-
OK. Here's what I can tell you. I use two different accounts in chrome. In both of them I have cleared my cache and cookies. In one account it works just fine. In the other, I get the problem.
So, when I go to this current page, http://www.seomoz.org/q/q-a-performance-improvements, and click on "reply" I get a brand new page on which to enter my reply. The url of the new page is http://www.seomoz.org/q/reply/122471/replies/new.
On that page, the javascript error console gives me this:
Hope that helps.