After migrating an existing forum over to discourse, I am now spending time correcting and re-organizing some of the categories. To my chagrin this causes old and inactive discussions to shoot to the top of the Latest and Categories views. I recommend a feature change:
An administrator or moderator correcting a title or category assignment should not IMHO count as “activity” which causes the topic to shoot to the top of the Latest and Categories views.
The current behavior is surfacing ancient topics as seeming to have recent activity when the actual discussion has not actually had any activity.
This only happens if your “topic” only has a single post. It is considered an edit to the “last post” which does bump a topic.
So it is kind of a specialized problem – why do you have so many topics that only have a single post? That’d be my first question, discussion topics consisting of a single post are not much of a discussion
What I’d like to do for the moment is clarify how the current features work.
If I change category or add tags to topics in bulk the “activity” value of the topics is not updated.
If I change category or edit the tags from within an individual topic, however, the “activity” value is updated.
This discrepancy caught me by surprise.
I tried reverting the edits I made in the latter case, but the “activity” value seems to be independent of that. I was asking if there was a way to unring that bell (apart from going back to an earlier backup and starting over).
For future generations, consolidating the behavior, as Sam suggests, is a good idea.
The import data was just a pile of JSON files courtesy of Ning. It seemed easier to do the re-categorisation using Discourse’s UI.
Following your comment I looked into accessing Discourse’s database directly. I got as far as accessing it via pgAdmin, but failed to figure out if editing topics in bulk there was easier. But it’s very late and I’ll freely admit to having no idea what I’m doing. I’ll take a look tomorrow.
Although my hunch is that what I’ll end up doing is restoring an earlier backup and starting again using the built-in bulk tools. Which is fine now that (I think) I’ve worked out a process. I was really confused earlier