As long as OP is someone who has ”legit right” to lift one comment (as solved one). And there is no issues to show nagging if that topic still continues.
That’s unnecessary noise for the rest of us? Rather than Posting, consider using the watching system and set the topic to “Watching” using the dropdown control at bottom left of the Topic. You can also use the Bookmarking system and create a reminder. If you like an idea you only have to hit Like too, instead of taking up a post just verbalising that.
You might want to use Discourse terms to describe your use case:
- Thread = Topic
- Comment = Post
A Post is not a Topic, a Topic consists of Posts, though I guess you can “post a Topic”
I’m not 100% sure I have the right idea, but are you wanting to visibly mark a topic as ‘out-of-date’, and include a link to the newer information?
If so, you could use a Staff Notice on the OP. Something like:
I also added a “knowledge-archive” tag for good measure to take advantage of the tagging capabilities if you need them.
I run into this scenario often, as it’s useful to understand why we decided something, with the historical conversation.
- Have your discussion topic, with all kinds of useful information (“Where should we have lunch?”)
- Move the useful information into a new topic (“Places to have lunch”)
- Reply to discussion topic with a link a short description, and mark that reply as the “Solution”, which will show prominently in the first topic
Thanks for the input everyone! Now we have a solid list of lunch spots at https://forums.example.org/t/places-to-have-lunch/1337. Check it out!
A bonus to this method is that it pairs well with other methods you may deploy over time, such as combining it with Discourse Docs, or long megathreads, or topics with auto-deleting replies… lots of combos for different ways of collaborating.
We have tech-oriented topics that are aging but we want to keep the text of the OP intact. At the same time, we don’t want readers to think that the text of the OP is necessarily complete. Our idea of an elegant solution is to pin a post directly beneath the OP which will contain any updates that we come across.
Does this help clarify our need?
What about updates to the update? Are you going to create subsequent replies which roll up all the updates and then pin those? Or will you need to pin multiple responses?
The reason this doesn’t have an immediate and obvious solution is because this is typically the domain of wiki posts. The current latest is presented, with previous versions still there for review.
Thanks, Stephen. Not having the necessary privileges, I wasn’t aware that wiki posts existed. (That’s because I’m trying to solve this issue for the org I work for.) But a wiki posts does sound like a good solution – assuming we can control the pinning of the wiki post directly beneath the OP. Do you know if that is possible?
The wiki is always the first post in the topic.
So everyone can update and curate with OP, with edit history available to all.
Thanks again. It if the wiki post is always the first in the topic, then apparently it would be placed directly above the OP, not directly below it. Is that correct?
Also, though I’m not an administrator, I’m not a beginner either. I’ve posted often on the forum, and yet I don’t see the menu when I click on the […] button; the […] simply expands to show the “bookmark” button. This is a bit confusing.
No. OP is wiki then.
OK, then it looks like we’ll have to live with the wiki post being the OP in those cases.
Thanks! Appreciate the help!
I shared the wiki post idea with my colleagues, including the forum moderator who created a wiki post for us to play with.
The one problem is that the post we designated as a wiki does not move to the top. We haven’t experimented extensively, but having this powerful wiki feature in a topic doesn’t do us much good if it’s lost in a random place in the posts.
any ideas here?
Not sure if this will work but reply and change the timestamp so it would be the oldest reply bumping it to the top.
I liked your thinking, but I’ve just checked and Change Timestamp is only in the topic wrench, not the post wrench, so I don’t think it would be an easy option.
The Make Wiki option is a default Trust Level 3 perk (though this can be adjusted in the
min trust to allow self wiki admin setting), which allows the post to become editable by anybody TL1 or higher (also adjustable). Wikis don’t have to be the OP, but they do tend to get lost if they’re not. Though you can search for them using the
in:wiki search filter.
With a wiki as an OP, it allows it to be updated with new information/edits by the community (depending on the TL settings you choose), and the previous versions can be viewed through the edit history (in top right corner).
I’m not sure that fits with what you’re after, but I still can’t quite fully see what your end result would look like. Could you give me a rough example of the first few posts in such a topic so I can have a go at replicating it on my test site?
@JammyDodger Thanks for the clarification on why I wasn’t seeing the dropdown menu when clicking on the […] item below a post.
And yes, I’m glad to provide an example:
This is one of our SoK (Systematization of Knowledge) topics that would be a prime candidate for adding ongoing updates via a wiki post while leaving the OP unchanged. Again, we’re almost there; if the wiki post automatically moved to the top of the topic (as @Stephen said it would) then we’d consider the problem solved.
Please let me know if this helps, and if you have any other questions.
Would it be possible to create the second post straight after the first as a placeholder, and use that as an ‘Update’ post when you need it? It wouldn’t even have to be a Wiki, as TL4 and staff have global edit, so can edit it as and when.
In theory, yes that would be possible. But is it necessary? Do you have any sense of what @Stephen had in mind in his comment above when he said “the wiki is always the first post in the topic”? Did he and I just miscommunicate?
It’s usual to make the OP the wiki post, though it does work on any post. But if you make eg. post 40 in a topic a wiki, it won’t change its place in the post order.
@JammyDodger Thanks again. I think that clears up the issue for the future. Going forward, we’ll create a post right after the OP as a placeholder for a future wiki post that would contain any updates.
Unfortunately, that won’t help us for our past posts that need the same thing. Do you have a suggestion for how we could slip a post into an existing sequence in the #2 position?