Yes I think this ↑ ↑ is an excellent starting point 
2개의 좋아요
I am struggling with this. Closing the wiki doesn’t work for me for the same reasons mentioned. It’s makes total sense to have the first post as the wiki, and the subsequent posts for discussion. Any edits to the first post should bump the topic to the top of the list. Users on the forum are checking latest and complaining why the edits aren’t being bumped.
The solutions mentioned here are exactly what I wanted to happen. Can this not be added?
Also see : Updating a wiki post, doesn't put it to the top of latest - #3 by Tim_Jefferies
If you need that, set the notification level for the topic to “watching” – watching a wiki topic will cause you to get notified every time the first post is edited.
3개의 좋아요
Users are complaining because the /latest part of the website doesn’t do what it says it does. Bumping the topic on the edit of the first post specifically for wiki posts is the logical solution. I understand that people use wiki’s differently, but having an option to change this behaviour makes a lot of sense.
My users don’t want to ‘watch’ wikis, they want to use the /latest page in the way that makes logical sense.
Locking a post, deleting extraneous entries, making sure to edit the last post every time I edit a wiki on split wikis (that hit the 90,000) limit, setting it to watching. These are not logical solutions, they are workarounds. Doing it for 1 wiki - no problem. But the more wiki’s there are the more exponential that work becomes to manage. I’d literally need to come up with a time-consuming moderator management process just to ensure people can see updates, and they will still complain, because they won’t be in /latest.
Fair, but the more you run into limitations like this, the more it indicates maybe you should pick a different free open source software, one that better matches your needs?
Having a bunch of 90k+ character wikis is not the target use case for Discourse in general.. and forcing a round peg into a square hole usually doesn’t end well.
2개의 좋아요
This software fits my needs very well. The reason for this feature request is pretty clear. Its a logical request that would improve an already existing functionality, and solve all the workarounds in the process.
I’m glad you like Discourse, cheers, but I don’t agree that “bump for any edit on any post in the topic” is ever a desirable behavior, versus the simple solutions outlined above..
2개의 좋아요
They aren’t simple solutions for users, or moderators. See first post in the topic.
I don’t agree that “bump for any edit on any post in the topic” is ever a desirable behavior
For wiki posts, it is desirable. And expected from users.
Having a bunch of 90k+ character wikis
I have one wiki like this. Whether they are long wiki’s or short wikis, our users still are requesting /latest to include wiki updates.
For a wiki it’s desirable, Wiki Posts =! Wikis. There are lots of wiki features which Discourse doesn’t have, this is one of them.
Are there any other discussion products which do this? Sounds like you need to consider a product like MediaWiki.
깨져 있지 않다고 생각하는 것들에 대해 핵심 업데이트를 피하려는 이유를 이해합니다. 하지만 제 (권고하지 않은) 의견으로는, 위키 게시물에 대한 수정이 게시물 순위를 올리지 않는 것은 사용자 입장에서 버그처럼 보입니다.
저도 이 문제를 우회하기 위해 주제를 닫고 OP(첫 게시물) 아래에 있는 모든 게시물(“주제 닫힘” 공지 포함)을 삭제하는 방법을 사용하고 있습니다. 하지만 제 위키 게시물은 몇 개에 불과해서, 이 방법이 확장성 면에서 잘 작동하지는 않을 것 같습니다.
더 정확히는 "주제 내의 모든 위키 게시물에 대한 모든 수정 시 순위를 올린다"거나, 심지어 "위키인 경우 주제 내의 첫 게시물에 대한 수정 시 순위를 올린다"가 더 적절할 것 같습니다.
솔직히 말해서, "위키 게시물"과 같은 기능이 있는 다른 토론 제품은 알지 못합니다.
여기 #contribute:feature에서 몇 가지 요청은 핵심 기능으로 적합하지 않다고 판단되어 거절되기도 하는데, 이는 괜찮은 일입니다. 우리는 단지 옵션들과 핵심 기능에 무엇이 포함될지에 대해 논의하고 있을 뿐이며, 핵심 기능에 무엇을 포함할지는核心团队(코어 팀)이 결정할 문제입니다. 하지만 이 문제는 플러그인으로 해결할 수 있을까요? 게시물 수정 시 훅(hook)을 걸어서 그것이 위키 게시물인지 확인하고 주제 순위를 강제로 올릴 수 있을까요?
8개의 좋아요
Most likely yes! Seems like a fine plugin idea as well.
5개의 좋아요
Best of all it keeps the confusing behavior out of core: