When your post gets rejected by a staff this is the message that is shown
Hi [user],
We’ve reviewed your new topic titled “[topic titles]” and have some feedback for you.
Reason: N/a
Feedback: This is what it shows when your post is given feedback
You can edit your topic’s original post below and re-submit to make the suggested changes, or reply to this message if you have any questions.
But you cant actually edit the post because nothing appears below it
this is a picture of the PM that is sent to this test user after they created a post that needed approval of it and it was rejected with a revision
and there is nothing there to edit below
So my request is that discourse adds the ability to actually edit the post itself on the PM and then it autoresubmits the post there for you on the forum and then the mods can re-reveiw it
좋은 지적입니다! 이 문제는 인터페이스의 언어와 관련이 있어 Contribute > UX 채널로 이동했습니다.
모더레이터에게 받은 개인 메시지(PM)를 검색해 비슷한 내용을 찾았습니다. 첨부해 주신 스크린샷과 PM에서 복사한 텍스트를 확인해 보면, 피드백을 받는 사용자가 작성한 부분은 "test post for meta topic here"입니다. 나머지는 템플릿에 포함된 내용입니다.
말씀하신 대로 "아래"에 있는 게시글을 수정할 수 없기 때문에 이 안내 문구가 혼란을 주고 있습니다. 수정하려면 해당 토픽으로 돌아가서 거기서 수정해야 합니다. 아니면 모더레이터와 논의하기 위해 답글을 달 수 있습니다.
이 변경은 UI를 너무 복잡하게 만들기 때문에 불가능할 것 같습니다.
여기서는 다음과 같이 안내 문구를 개선하는 것이 해결책이 될 것 같습니다:
제안된 내용을 반영하기 위해 게시글을 수정하거나, 질문이 있으시면 이 메시지에 답글을 남겨 주세요.
that would work as well but the thing is once the moderators reject the post It no longer can be edited it sends the Pm but then they need to go back and recreate the post.
Furthermore I think maybe if it created a reply or a draft in your account draft pages to remake the post with the title there and then you resubmit that
let me know if that makes sense
additionally adding the link would mean that rejecting the post couldn’t delete it because then they can’t go and assess their post again?
Oh, I see. The review queue is just providing a copy of the (now deleted) post for convenience for the user, so they can copy it into a new post and improve it there. That makes it even easier:
Your post has been deleted but a copy is provided below for your convenience. Please post it again with the suggested changes, or reply to this message if you have any questions.
Being able to edit the pending ‘post/topic’ [1] would be great though, and would really smooth out this experience for users. I think there was some talk of this in the past.
Currently the pending posts show in the post stream as well as in your /activity/pending(that page has both pending posts and topics), but you can only delete and not revise them. If they could be made editable in a similar way as the review queue allows admin/moderators to then handling the approval with ‘Revise’ could avoid deleting it and allow it to remain as ‘pending’. The feedback PM could then have a link to make it easy to navigate to, edit, and resubmit.
There may be some rough edges to smooth out to prevent editing by user and mod at the same time, but maybe some of the new auto reviewable claiming could help with that and provide an edit lock.
There would also need to be some allowance made for the Reviewable after it had been handled as Revise, as theoretically the flag would have been handled, but would also still be pending. (And you perhaps wouldn’t want that sitting as a live flag in your review queue while you wait for an indeterminate amount of time for the revision, which may never come).
I don’t think it’s actually a post/topic at this point, but rather a precursor ↩︎
I think the new changes being worked on in the review queue will allow assigning flagged items to other people.. maybe in this case it could be assigned back to the user who posted it?
I think a system that can allow for the real possibility of ‘abandonment’ may be needed. So something that can self-tidy after a reasonable timeframe.
Possibly something clever like the original pending item being deleted but immediately replaced with a duplicate so it looks exactly the same to the user but can then create a new reviewable in the queue when resubmitted.
Possibly also a delete-timer in a similar fashion to Delete removed posts after (with a more reasonable ‘revision time window’ than 24 hours)
Not really though if the user who’s post got rejected with the feedback may not be around to view the rejection then comes around 2 days later the 24 hour deletion timer would have not let them come back to edit it and this may cause some issues in different forums?
Perhaps its auto set to 24 hours maybe and then in something in the admin dashboard they can change the auto timer?
Ah, sorry for the confusion. I was referring to the default for the existing Delete removed posts after admin setting being 24 hours, and that while a similar function could also be applied here to ensure pending posts were not sticking around forever it would need a much more generous time window.
Hmm. Not really. Though if the product team are interested in the idea, and the dev team think that’s the best way to implement it then I’m not against it.
But in my mind it would stay as a pending ‘item’ and be editable from your /pending page (with at least the appearance of it being a post/topic). The PM you receive on ‘Revise’ would ostensibly be the same as now but with a link directing you to where the pending item can be edited, and a generic ‘you have {30 days} to revise and resubmit your contribution before it’s automatically deleted’ (or some such)
that actually is a good idea makes the most sense
but wouldn’t it really mess up the UX for the hole rework of the Reviw and add the newest addition with the message? @JammyDodger
I mean, a lot of this is just ideas and the dev team [1] could well say that the picture I have in my mind is not the best way/is just simply unworkable.
But I think if the first pending item is treated as its own entity (that is, the flag is handled, a PM is sent, the reviewable is no longer pending) and a second, duplicate pending entity is created to allow for editing and resubmitting then it could then be popped in the approval queue as a ‘new’ reviewable once resubmitted. The pending item awaiting revision could be marked clearly as such on the /pending page as well to reduce confusion (is it waiting for mod approval/is it waiting for me to revise?)
I’m not 100% sure I understand the question, but I was thinking of a flow something like this:
flowchart TD
A[Post/Topic Created] --> B[Pending in Approval Queue]
B --> C[Revise]
C --> D[Pending Awaiting Revision]
D --> E[Resubmit]
E --> B[Pending in Approval Queue]
B --> H[Approve Post/Topic] --> I[Published to Site]
B --> F[Reject Post/Topic] --> G[Deleted]
style F fill:#ff4c4c,stroke:#000,stroke-width:2px
style H fill:#4caf50,stroke:#000,stroke-width:2px
So any second/third/fourth revisions would loop round (and a mod could call time manually when enough was enough )
I think I envisage the ‘Revise’ option being used in cases where there is a higher likelihood of receiving a better version (so anything that doesn’t hit that threshold wouldn’t be sent back for revision in the first place)
Ok that makes more sense but suppose we added a setting for the multiple revision called post rejected reviews delte where admins set after (x) revision denies it removes the post automatically to prevent times of revision?
Regarding the complexity of the interface: I think it could use a method similar to the one in the discobot tutorial, where the system automatically sends a reply in this PM using the user’s identity and containing the content to be edited, so that the user can obtain ownership of the post to be edited. Moreover, this requires no changes to the external interface and no functional extensions to the original messages sent by the system. The remaining part is the issue of the process for triggering the review upon editing (which do you think is better: automatically triggering the review after each edit, or having the user manually trigger it by clicking a certain button or sending a subsequent reply containing a specific word?).
최근에 이 문제를 겪었는데, 현재 상태가 이상적이지 않다는 데 동의합니다. 당분간 이 문제를 개선할 수 있는 가장 간단한 방법은 거절된 게시물의 내용을 초안으로 생성한 후, 사용자가 해당 초안으로 이동하여 수정하고 다시 게시할 수 있도록 링크를 제공하는 것이라고 생각합니다.
times of revision?