-
Notifications
You must be signed in to change notification settings - Fork 0
WM - Forum link is not active for the Active challenges #614
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
Comments
@coderhacker - Can you post a sample challenge ID or two please? |
cc @rootelement |
@jmgasper I have added the above challenges ID |
@coderhacker - Are those launched under a group? I see a strange error when I try to pull details on the challenge:
|
Yes there is Work Manager App. which have forum link. currently this forum link is inactive |
@coderhacker - I'm thinking the group may be an issue. Is the group setup the same in prod? |
Nope, we are using for prod this group Groups: Hide Challenges |
What's the prod challenge that uses that group? |
Here is ID for prod a5b69350-82d6-4955-807a-3b47b5678b70 |
@coderhacker - Ok, thanks. That helps rule out the groups idea I had. For 452751f3-1418-496b-92e0-5e142a902b7f, I can see that the discussions object just doesn't have the The group on Vanilla actually did get created just fine (https://vanilla.topcoder-dev.com/categories/452751f3-1418-496b-92e0-5e142a902b7f), it's just not linked back to the challenge metadata in the Topcoder API for some reason. I'd like to test with a new challenge that you create, while I'm watching the logs. That will help me see what happens / what errors pop up. Feel free to reach out in Slack so we can coordinate that.
|
cc @sdgun |
Expected behavior
Forum link is available for the Active challenges, this should be active.
Please note: This is working on the Production environment. please see attached screenshot

Actual behavior
The Forum link is not active for the Active challenges for all track
Steps to reproduce the problem
Screenshot/screencast
Attach or link a resource.

--
Environment
The text was updated successfully, but these errors were encountered: