Arrows not working
The up and down vote arrows on electrical engineering don't appear to work. Noticed it yesterday for 1st time.
Guys, well-done; it's fixed now (at least on meta) and I'll try on EE shortly.
Sept 7th testing after deleting cookies - successful!!
3 answers
Thank you for reporting this very frustrating problem. We've had scattered reports of this and are investigating why some people cannot vote, comment, or post and others can. One thing that has helped some people is to log out and back in again. If that doesn't fix it, you can delete cookies from electrical.codidact.com (or other affected community) in your browser. It's specifically the session cookie, if your browser lets you target individual cookies. (Sorry, I don't know how to identify it, since my browser apparently doesn't give me that degree of control.)
We (by which I probably mean "someone with actual technical knowledge") will update when we know more.
Update 2025-09-20: We deployed more changes today that we believe have finally fixed the spurious errors that some people were seeing with voting, editing, and comments. Please let us know if problems continue, and thank you for your patience as we worked through all this.
1 comment thread
We're hoping this problem should be fixed now.
If anyone is still experiencing issues, please try logging out, removing the codidact_acct cookie, then logging back in.
I couldn't vote either, and had additional problems with various other buttons not working. At one point I had logged out of Codidact and couldn't log back in again.
I am using Microsoft Edge on Windows 10, and ended up clearing all stored data, like cookies. I couldn't find how to clear stored data related only to a particular web site. After restarting the browser and logging into Codidact again, everything seems to work now.
Hopefully this gives the web team another clue as to what may be wrong.
It broke again just a day later with the same symptoms. I just now cleared all browser stored data for codicat.com and now everything is fine - for now.
Next time I came here after closing the browser, the problem was back. Apparently clearing Codidact cookies fixes it for one browser session only.

2 comment threads