Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to re-assign the connected discourse category for a group #219

Open
nukeador opened this issue Jan 10, 2020 · 6 comments
Open

Ability to re-assign the connected discourse category for a group #219

nukeador opened this issue Jan 10, 2020 · 6 comments

Comments

@nukeador
Copy link

@nukeador nukeador commented Jan 10, 2020

We need the ability to change the destination discourse category for some groups, like the curated Reps group, which already has a discourse category:

https://discourse.mozilla.org/c/reps/

@nukeador

This comment has been minimized.

Copy link
Author

@nukeador nukeador commented Jan 10, 2020

Clarification: We might want to do this as ad-hoc need, not something that we will usually do from the admin interface. So if this is something we can request to change on the database it would be highly appreciated, I expect no more than 5-6 groups in this situation.

@nukeador

This comment has been minimized.

Copy link
Author

@nukeador nukeador commented Jan 21, 2020

@LeoMcA will be talking with @dnaluz about this to understand the best approach.

@LeoMcA

This comment has been minimized.

Copy link

@LeoMcA LeoMcA commented Jan 23, 2020

Provided none of the /categories/ endpoints are called on the non-/c/community-portal/blah category, then the api shouldn't spit out any errors.

User addition/removal from the group can still be synced with /groups/{id}/users, and I can manually link that group to the existing discourse category for notification purposes.

The get a list of topics api can be used on any category (as it's ready only).

@nukeador

This comment has been minimized.

Copy link
Author

@nukeador nukeador commented Jan 23, 2020

So if I understand this correctly, changing the destination discourse category ID from the portal shouldn't through any issues.

@dnaluz

This comment has been minimized.

Copy link
Collaborator

@dnaluz dnaluz commented Jan 23, 2020

@nukeador I don't have access to your production database, so doing an ad-hoc solution is not viable. Also the way the meta data is stored in a non readable way so updating the data manually would not be easy. Creating an interface in the admin would be easier, the only thing stored on the wordpress side is the group / category ids, anytime we need to pull data I do a get on the category / group, so I wouldn't need to sync anything on this side.

@dnaluz

This comment has been minimized.

Copy link
Collaborator

@dnaluz dnaluz commented Jan 23, 2020

As long as the proper cateogry id is used, but there is no way for me to verify which is the "correct" category id. Also you would need to find the id from the discourse side we wouldn't be searching from the portal side for the proper id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.