When I choose to “Update Notifications” from the “Bulk Actions” drop down, and do NOT choose any of the radio buttons from the modal that pops up, and then click confirm button with none of the radio buttons selected the topic disappears from my users view forever. I am not sure how to bring it back or if it is even possible. I verified that for other users the topic is still visible so it is not deleted entirely from the database.
I am thinking that in this modal that pops up the Confirm button should NOT be enabled unless one of the radio buttons has been selected.
Steps to Reproduce:
Select one or more threads and click ‘Bulk Actions’
Select ‘Update Notifications’
In the modal that appears leave all the radio buttons unselected and click next. You should see that the Thread just disappears for that user seemingly forever.
I think the topic was muted. You can find it by adding ?state=muted to the URL.
So if you mute a topic here at Meta, you can find it at https://meta.discourse.org/latest?state=muted.
I agree with you that muting can be very confusing if it was not intentionally selected.
Thank you for the report. I can indeed reproduce this - it seems that the muted option is being set if the confirm button is clicked and no options chosen.
to see all your muted topics and unmute them, you can use the filter /?state=muted as in https://yourforum.org/?state=muted
Thank you both for the quick response! Yep, from your instruction I verified they are going to muted state. So at least I have a work around to recover them!
Is this fix expected to be in 3.5.0.beta8-dev (0f2996a3b3)?
I successfully upgraded my server to this level but I am still seeing the “Confirm” button enabled and when I click it the threads are no longer going to “muted” state (which is good!), however I receive a couple of these ugly error pop ups when clicking “Confirm”. I’m attaching the browser console logs in case that is helpful. forums.packfansnation.com-1751029729681.txt (8.8 KB)
(Edit: Also (apologies as I’m very fresh to discourse ecosystem) I’m not unsure of the process for re-opening a bug. I see this is marked as fixed/completed so hopefully this is okay to just reply here, if not I’m happy to open a new bug topic)
This means you have the fix and its working server side.
My guess is there is a javascript conflict somewhere preventing this from working. Could you run your site in safe mode and then see if it disables the “Confirm” button if nothing is selected?
@blake I am still seeing the same issue in safe mode. Confirm button is still enabled there, and I still get the 2 error UI pop-ups.
When I upgraded I did it through the UI only (/admin/updates). That was my very first ever update of the server to a new version. Did I need to do a “./launcher rebuild app” as well?
No, you shouldn’t have to. Unless its unable to upgrade in the ui and then it will tell you do use “./launcher rebuild app”.
What browser are you using? Maybe something is cached on the frontend? I can try another fix, but the current fix is already working on other discourse sites so I’m just trying to narrow down what the issues might be.
Can you take a screenshot of your browser with the console open when you open that model? The text file you sent over earlier wasn’t really helpful.
@blake I’ve now tried in these 3 browsers, and in ‘incognito mode’ as well, and it reproducible everywhere, pointing to it being specific to my discourse server
Edge Version 138.0.3351.55 (Official build) (64-bit)
Firefox 140.0 (64-bit)
Chrome Version 137.0.7151.120 (Official Build) (64-bit)
Note, this is after clicking the ‘Confirm’ button in the modal.
@blake for giggles I did the ./launcher rebuild app command and that fixed it. The confirm button is no longer enabled if no radio checkbox is selected.
Something wonky must have happened with the update via the UI from beta7 to beta8. After the update My server gave me the smiley face and said everything upgraded fine, but seems like it only applied half the fix for this issue.
Either way, I’m good to go now and I can just ensure to do my updates from the command line going forward.
