[meta][forum] Votes are not given back when topic is closed

I have no idea what category or tags to use for this little bug request, please fix as needed

A topic was closed, and yet my vote was not retuned to me. I expect the vote to be returned to me on topic closure.

I don’t know if BW hosts their own Discourse instance or if you use CDCK/Discourse provided hosting where they manage everything for you.
Maybe it’s the Voting plugin which wasn’t updated when you updated discourse in case you self-host, maybe it’s a bug in the plugin itself, but I wanted to point this out.
If you want, i can cross post on https://meta.discourse.org as well.

Topic: ✅ Consistent behaviour on clicking a listed item in vault

Screenshots showing my vote to the topic:


Interesting, because my own vote on the same topic was released, as expected:

image

 

Have you tried logging out and logging back in to the forum (and clearing your browser cache)?

I did not try to relogin in the main browser profile, however i did try to use Private browsing mode and ended up with the same problem.

Tagging @bw-admin @dwbit to see if they can look into this issue for you.

Looks like there was indeed a bug: Votes not being returned on topic close - #11 by JammyDodger - Bug - Discourse Meta

Looks like won’t be an issue for future posts but may need to manually adjust existing posts as they change state.

That’s a very old topic (end of 2023). This means that possibly a large number of BW forum users might be affected by this voting bug.

Does this also mean that BW forum wasn’t updated in a very long time? Or that i cast my vote before end of 2023? That’s unclear to me after reading (diagonally :blush: ]) the discourse topic.

Anyway, as far as i can see, i (every user?) has to take their vote themselves, as the vote was still not released even after opening and closing the topic. I have 2 notifications that the vote was released, but i still see the vote on the topic.

notifications:

opening/closing:

vote still not released:

If this will happen again, I’ll ping here again as well. Maybe there’s a different bug which we have to raise to discourse.