angus
October 27, 2022, 12:16pm
469
Hey guys, as discussed in the topic above I’ve already written a migration feature of Retort to Reactions, including an admin UI.
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…
For it to be production ready the maintainers of Reactions will need to make a slight change to improve the abstraction of the code in the Reactions plugin.
Yup, I could do that. It would be a bit of a hack though
Supporting a production level migration between two plugins like this requires significant quality assurance otherwise issues like this can easily occur.
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.
…
3 Likes