Hi @riking, thank you for responding… AFAIK apart from the PostReplyKey there’s no mention of this missing user id. But it might not be the actual old user id since I do not know that one. How do you think I could find it – or: what should I grep from the logs?
It might be the discourse-assign plugin as it seems to be the only plugin in your list that modifies the TopicQuery class. And I suspect that’s where the error occurs.
Can you verify my suspicion by disabling the plugin and checking if the category works? You can re-enable it afterwards. Also, it would be interesting to know if any of the topic’s custom fields references the merged user in some way or another. Can you check that out as well please?
./launcher enter app
id_of_problematic_topic = 123
In fact, perhaps you could work with @fzngagan on a migration script from Events to Discourse Events? It’d be good to have a real case to work with there. Faiz, we should prioritise this, I’d like to formally deprecate Events.
@angus, @fzngagan: do you think I can change the plugin line in the container configuration, rebuild, and then take care of running the script? Since I also need to change the git repositories for who’s who and wizards, I could do it at once. OTOH we’re in the middle of a hackathon and if the problem is solved I can as well wait for a week.
I’ll throw my hat in the ring for working on a migration script.
I’m a heavy user of Events. My Plugin for schools with children with behavioural difficulties creates 7 topics a day for 10+ children across multiple sites and has been running for over two years. Each topic represents a period of their school day and I need to be able to query by topic event date so I hope Discourse Events stores its data in a sympathetic place.
Yes, we’d like to keep past events since they’re related to topics, especially the current ones related to the (still ongoing) ActivityPub conference 2020 – this week is the hackathon.
Apart from those we do not have many events, but will read about the migration – probably next week since this week is already more than full. Cheers! And what @aschrijver said: the Discourse community rocks!