Discourse Retort

[angus (Angus McLeod)]

여러분, 위 토픽에서 논의했듯이, 저는 이미 Retort에서 Reactions로의 마이그레이션 기능을 관리자 UI와 함께 작성해 두었습니다.

Discourse Retort

I’ve written a migration script and created an admin UI to migrate retorts to reactions. It’s on this branch. The UI looks like this [Screen Shot 2021-03-18 at 4.30.04 PM] I need some advice to finish it off. It’s possible that a user could have both liked and “retorted” on a post. In the migration, I’m going to preference retorts over likes in this scenario. However the ReactionManager.toggle! access protections do not allow this. Would it be possible to add a “force” option for migrations…

이 기능이 프로덕션 환경에서 사용 가능하려면, Reactions 플러그인 유지보수 담당자가 Reactions 플러그인 내 코드 추상화를 개선하기 위해 소규모 수정을 해야 합니다.

Discourse Retort

Yup, I could do that. It would be a bit of a hack though I’m not sure I could assume that workaround would remain viable over time. It’s also a bit risky. For example, if I just run that code the user’s post_undo_action_window_mins site setting would remained changed. You could change it back at the end of the migration, but doing setting changes like this on the fly to get around a guardian is not ideal. Ideally what I’m after here is a slight change to the ReactionManager interface to…

이러한 두 플러그인 간의 프로덕션 레벨 마이그레이션을 지원하는 데에는 상당한 품질 보증이 필요하며, 그렇지 않으면 이와 같은 문제가 쉽게 발생할 수 있습니다.

재구축 중 오류를 일으키는 플러그인

What is happening here is this Some people have a very old version of the question answer plugin with my personal github username in the repository URL in their app.yml file. I transferred the QnA plugin to paviliondev years ago. Github redirects repository URLs when they’re transferred, so the old urls with my personal username in it kept working. More years later Pavilion transferred the Question Answer Plugin to Discourse. Discourse initially kept the name discourse-question-answer. …