Previously we ran into issues with upgrading to the latest version of Discourse, this turned out to be related to the Assign Plugin/ Production Data issue that @angus helped us identity and resolve by removing the plugin. Moving forward we would like to reinstate the plugin but need to eliminate th…

After going back and forth with @Roman on this, we were able to finally get this resolved! After running the query that Roman wrote to eliminate a data conflict, adding the Assign plugin and then rebuilding the app, I was met with success! Roman has been a huge asset through this whole ordeal and …

Are you sure “group id 3 admins” is correct? app/models/group.rb main after_commit :automatic_group_membership, on: %i[create update] after_commit :trigger_group_created_event, on: :create after_commit :trigger_group_updated_event, on: :upda…

@Mittineague I confirmed this morning that the group id for admins is indeed the default group ID. [05%20AM] The log information I included was during our down time and we have temporarily removed the Assign plugin which immediately resolved the issue and allowed us to successfully leverage discou…

The value of the assign_allowed_on_groups site setting is in a bad state. We migrated from using group names to group IDs. (groups.id in (‘3’,‘admins’,’… admins should be replaced with the group ID to fix the issue.

[imagen] Roman: admins should be replaced with the group ID to fix the issue. How do I go about modifying that?

From your Discourse folder, you should: Enter the container running ./launcher enter app Open a Rails console running rails c Once inside the console, you can run this script to fix the issue: allowed_groups = SiteSetting.assign_allowed_on_groups.split('|') allowed_groups.map! do |ag| ag.to…

After doing the above suggested, I was not able to successfully run the script. Below is the output of the attempt. Any direction is highly appreciated :pray: app:/var/www/discourse# rails c [1] pry(main)> allowed_groups = SiteSetting.assign_allowed_on_groups.split('|') NoMethodError: undefined m…

Looks to me like you have an old version of Discourse assign installed … are you on tests-passed with latest discourse assign?

Let me look into this @sam and I will let you know what I find :+1:

With the Assign Plugin currently removed @sam , you feel reinstalling the plugin with the latest version might be the best course of action?

@sam @angus I went to reinstall the Assign plugin again tonight and experience complete failure again after sign in. I captured logs of the failure but wouldn’t prefer not to post them publicly but willing to do so via DM. [03%20PM] Any suggestion on how to move forward?

Seguimiento: Asignar conflicto de plugin

Soporte

Roman (Roman Rizzi) 1 Octubre, 2019 12:00 23

¡Me alegra que hayamos podido solucionar este problema, Jim!

Cierro esto ahora, ya que este problema ya se está rastreando aquí:

Tema		Respuestas	Vistas
Discourse Assign - bug taking site down Bug	16	1158	16 Marzo 2020
Failed upgrade from 2.3.2 to 2.3.6 due to discourse assign plugin Self-hosting	6	684	2 Diciembre 2019
Today error when upgrade from 2.5.1 to 2.5.2, discourse-assign Self-hosting	5	905	6 Noviembre 2020
Discourse-assign plugin isn't working Support	3	601	6 Diciembre 2019
Loading groups gives internal server error Support	13	959	2 Noviembre 2021

Seguimiento: Asignar conflicto de plugin

Temas relacionados