Original title: Forum front page inaccessible (blank screen or 404) I am moderator at the SocialHub forum at https://socialhub.activitypub.rocks which is the technology forum for the ActivityPub protocol that drives the Fediverse social realm. Currently there is a 4-day ActivityPub Conference going…

After disabling discourse-assign: latest works top fails /t/951 still fails Running the query… Ah! You nailed it! {"event_start"=>1601748000, "event_end"=>1601749800, "event_all_day"=>false, "event_timezone"=>"Etc/UTC", "event_rsvp"=>true, "event_going_max"=>100, "event_version"=>1, "event_goin…

PostReplyKey refers to the reply-to address in emails, it won’t interact with topic list rendering. Checking the stacktrace, it’s failing inside TopicListSerializer dumping, somehow inside lib/instance/public.rb. Try checking the topic featured users list for the old user ID (the set of avatars th…

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 ActivityPub Conference 2020 - SocialHub category is now visible again. Now I guess there’s a refe…

Do you have a stacktrace for that error?

Nothing more than what I posted in User merge failed, corrupted database entries due to third party plugin - #4 by hellekin and commented after: [image] hellekin: I think the problem comes with ActiveRecord::RecordNotFound (Couldn't find all Users with 'id': (36, 50) (found 1 results, but was l…

Oh, I missed the stacktrace in User merge failed, corrupted database entries due to third party plugin - #4 by hellekin . 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 pleas…

OK fetching that… I have connectivity issues. I’ll check with safe_mode to see if it works. Safe-mode does not help… hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.co…

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 w…

You can update the custom field of that topic and remove the non-existent ID. @angus might want to add support for user merging to his plugin. [image] Rake task for merging users Plugin authors can hook into the merge process by handling the :merging_users event. I’ve already implemented it for …

Fusion d'utilisateur échouée, entrées de base de données corrompues dues à un plugin tiers

Soutien

gerhard (Gerhard Schlager) Octobre 5, 2020, 7:08 24

Vous pouvez mettre à jour le champ personnalisé de ce sujet et supprimer l’ID inexistant. @angus pourrait souhaiter ajouter la prise en charge de la fusion des utilisateurs à son plugin.

Sujet		Réponses	Vues
Issue merging user accounts, web interace and rake console Support merge-user	10	432	Mai 14, 2025
Discourse 2.5.0.beta3 Release Notes Announcements release-notes	1	4644	Avril 22, 2020
`NoMethodError in TopicsController#show` error after merging topics Bug pr-welcome , calendar-and-events	3	121	Juin 27, 2025
Merge users not possible from UI or CLI Support merge-user	2	493	Mai 14, 2025
Failed to process hijacked response correctly : Couldn't find Topic with 'id'=569 Bug	14	1645	Novembre 26, 2018

Fusion d'utilisateur échouée, entrées de base de données corrompues dues à un plugin tiers

Sujets connexes