Lately our community has been seeing topics being closed after the first post without any staff action or system record. I cannot find any record in Settings >> Logs >> Staff Actions either. Any hint on what is causing the auto-closure, which has never happened before? Thanks!
There are category settings you can configure to have topics automatically close. However, I believe even any changes to those are logged, but it wouldn’t hurt to check.
Yup, same thing happening over on the Manjaro forum.
- Installed: 2.8.0.beta4: ( 00820f0fad )
- Topic closed but no Mod logs about how it was closed.
- Mods can reopen closed posts (or most of the time: delete them as the user started a new one)
- Seems to be happening to TL0 users only.
I can give you links to exact examples over on the Manjaro forum if that would be helpful?
My apologies for pinging you directly, but as this looks like a serious bug and I only know you and codehorror, and I’d rather
be kicked in the by you than him bother you than him…
|retort Reactions plugin for Discourse||1.2.3||Y|
In the meantime, we’ve activated unlimited edits on first posts, and are monitoring the issue closely!
Looking at your plugin list I would try to uninstall the unofficial plugin
since it seems the only one in the list that is acting on new users (TL0) and has not been updated for over 2 years
Uninstall it, rebuild the site and let us know how it goes.
Have you noticed if the closing is taking place in a single category or in several categories?
Have you noticed if it happens only in private or public categories or both?
We don’t have any unofficial plug-ins installed yet we are still experimenting the issue.
It happens in different categories on our site.
We only notice it happening in public categories, though our private categories are not active.
Please share a link to a closed topic on your site.
That page is 404
Topic has been deleted in the mean time…
Most were deleted as posters immediately created a new topic so most of them were duplicates…
Sorry our community has been actively reopening topics that have been closed by no one since this has been a known bug within our site for a while. I can only find screenshots of these topics when they were first reported:
The devs need the URL AFAIU… Did you take a screenshot including the URL somewhere?
So far the issue hasn’t cropped up any more, so if you’re testing this and can’t reproduce, please turn that setting off… @littleviolette So you would want to do the opposite of my advice to our lords and ladies of the development team…
And of course the moment I write this, It’s happening again!!! Most recent example:
My sincerest apologies for getting everyone’s hopes up!
And another one bites the dust:
Do you have enough examples now and should I
shut the hell up stop posting new ones? (I.E. not all moderators provide feedback to me, should I pester the ones that look into the newest of the newest posts to provide some more examples?)
Given this never happened on meta, my concern here is that this is something very specific about how manjaro forum is configured, a third party plugin interacting badly, something else?
We have not had a single report of this to the best of my knowledge across thousands of customers @tech-advocates?
Long time no hear and good to hear from you!
is only 1‰ off for thousands (2000?). so I do agree it seems to be an edge case, and if @littleviolette could post a link to
shouldn’t a DBA be able to
diff between whatever
both of us are doing wrong which obscure parameter we’ve both set and everyone else didn’t?
Alternatively could you provide us a method of comparing ourselves to everyone else as we have professional *nix Engineers, Oracle DBAs, devs, … in our community.
I cannot recall any reports. The only time I have seen this happen is when I’ve been tinkering around and use the rails console to manually set
true rather than using
Looking at the category this topic came from:
I notice that there are a variety of topic timers in play. This is the angle I would investigate and play around with @Fabby. If you can come up with a way to reproduce the issue, we’ll be happy to try to dig in! Things I would check/adjust include:
- Do you use the
solved topics auto close hourssite setting? If so and a post is marked as solved then unsolved, is the auto-close successfully canceled?
- Do you have the category set up to auto-close topics?
- Do your mods often manually add auto-close timers to topic or ever attempt to manually cancel existing timers?
- Are the topics with this issue topics that were moved between categories?
Just wanted to provide some feed-back: your suggestions have been copied over into our internal thread and the forum owners have been pinged. As they are also the Manjaro founders and maintainers, feedback might take longer than you’re used to until now…
Yes to this and no to everything else. Our topic auto-close timer is set to 2 months after the last active topic. The reported bug happens when there was only one post (the OP) before the topic got mysteriously closed. This also happens in categories that does not have an auto-close timer set.
I wonder if the issue is related to post deletion (either by the OP or the system). When I was trying to find sample links to affected topics, I noticed they have all been either moved by our moderators (for other reasons) or deleted by the system, after a mod has reopened the mysteriously closed thread. Here is a screenshot:
Can you copy-paste the URL to one of these, please?
The topics are no longer visible to public…