-
Notifications
You must be signed in to change notification settings - Fork 212
Migrate the Setting page into private group, e.g. topgear
#4088
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
Here's a challenge spec for this ticket, please take a look: https://docs.google.com/document/d/1-Zwb5QGPm2ByzAb_HE9LKtiEEefPScTCJA5HGSxvID4/edit?usp=sharing |
topgear
topgear
putting this on hold for now. |
In this ticket, we plan to support these private groups firstly to have https://topgear.topcoder-dev.com/ |
Could you tell why the deployed code in community#dev environment and my local deployed version are different for cs community ? https://take.ms/BJid1 Actually I tried otherwise private groups as well. Right now, it seems only topgear private group are the same between deployed locally and community#dev environment. https://take.ms/xq4Ou I suspect my changes to otherwise private groups not getting executed due to the route load balance in the community-app#dev environment. |
Hi @LieutenantRoger, I'm not sure about the why there's a difference between CS dev and your local version. I can look into it. Until then, let's narrow down the scope so excludes any private community with this issue. As long as we can get this complete for Topgear... |
Sure |
Thanks |
Settings link from the Profile redirects to Prod. Only the direct url shown above loads the Beta Settings page. |
All Settings sanity checked for this Profile on Beta. The changes seem to be set correctly. |
Hi @lakshmiathreya yes, it was due to the |
Verified on topgear.topcoder.com via Wipro login. |
Describe the bug
Migrate the Setting page into private group:
topgear
To Reproduce
Steps to reproduce the behavior:
https://topgear.topcoder-dev.com/members/TonyJ
TonyJ
in the top right area of the header to show a sub-headerTonyJ
public setting screen right now.Expected behavior
We need to migrate current SETTINGS page into private domain.
So after step 3, user should be remain in the private group with Setting section displayed, and the header should be still the Private domain header.
Additional context
The work should be down against,
feature-private-settings
The text was updated successfully, but these errors were encountered: