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?
If it is topic featured users, this query should find it:
SELECT id
FROM topics
WHERE featured_user1 = 1234
OR featured_user2 = 1234
OR featured_user3 = 1234
OR featured_user4 = 1234
OR last_post_user_id = 1234
The query returned no result with the old userid, but one topic with the new user id, which is the topic that was already identified as problematic. I moved the topic to another category and indeed the https://socialhub.activitypub.rocks/c/meeting/apconf2020/53 category is now visible again.
Now I guess thereās a reference to the missing user_id 36 somewhere in the data related to topic 951, but I could not find it so far. Or is there another dependency Iām overlooking, wrt user 295?
Oh, I missed the stacktrace in User merge failed, corrupted database entries, UI troubles. So, itās failing due to a plugin. I guess one of your plugins stored some kind of user information that hasnāt been merged. Could you give me a list of the installed plugins please?
I see already that I can upgrade the URL for the last ones. (but the rebuild can only happen tonight UTC like midnight)
Maybe ping @angus or @merefield for events and locations.
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
rails c
id_of_problematic_topic = 123
Topic.find(id_of_problematic_topic).custom_fields
Apparently the events plugin is skipped during merging. But that might be as well because itās an older version weāre running. Tell me if I can help you test this case.
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.
@hellekin
I recently fixed a similar issue where deleting a user was causing problems.
I love the idea of migrating to š Discourse Event . The question then is, do you wish to retain expired events, and how many upcoming events do you have?
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.
Iāll jump on the discussion you mentioned below.
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!