How to understand the "Solved" locked status

Support
1

image
image1042Ă—103 5.68 KB

The solution marked in the diagram does not have a checkbox next to the button and cannot be deselected.

Here is the situation: This is a self-hosted server for which I have Admin privileges. A topic was created by a test account with Moderator privileges (which I use to record some logs or experiences). I marked one of my own replies in that topic as the solution. Today, I wanted to replace the solutions for some old topics without destroying the existing records. So, I created new reply posts in those topics, deselected the old solution, and accepted the new one. This worked fine in topics I created myself. However, when it came to this topic created by another account, I found that I could not deselect the old solution.

  • I initially suspected it was a permission issue, so I used another test account with Admin privileges to revoke all special permissions from the account that posted the reply. The result was that I still couldn’t deselect it.

  • Subsequently, I suspected it might be because the creator of the reply post marked as the solution was not the topic creator. So, I switched to that Moderator account, but the result was the same – still couldn’t deselect it.

  • Later, I tried changing the ownership of the Original Post, attempting to resolve this by making the topic creator and the creator of the reply post the same user. However, it still displayed the locked state as shown in the diagram above.

Has anyone encountered a similar situation? I would like to hear about everyone’s experiences. :slightly_smiling_face:

:memo: Note

Except for the case where I switched to the Moderator account, in all other instances, the user attempting to deselect the old solution possessed Admin privileges.

An awkward fact is that I was unable to replicate this scenario through a similar process in other topics. :innocent:
It seems that this locking effect was not directly triggered by event operations, but also requires waiting for some timing processing.

1 Like
2

Is the topic locked? IIRC that could be one if the factors.

3

This remains the case even when open, and cannot be reproduced by first selecting a solution and then closing the topic. :thinking:

4

Sounds like a possible bug, if you inspect the page and look at the console tab when attempting to change the solution, does it produce any errors?

5

No, there is no relevant information in the console, only this ordinary content.

app.js:331 ℹ️ Discourse v2026.3.0-latest — https://github.com/discourse/discourse/commits/5907059890 — Ember v6.10.1
start-discourse-ed0c531d.js:4 [Intervention]Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113

As for changing the solution—I cannot attempt it because the solution is locked, and that location is not a clickable button, so there is actually no way to perform any operation.

1 Like