-
Notifications
You must be signed in to change notification settings - Fork 212
Private member profiles should be open up in a new browser tab #4082
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
@Oanh-and-only-Oanh For #1, we seems not having a challenge that can allow us to reproduce this in the |
#2, why a topgear user is able to click a member's handle in public domain ? I seems could only think up that this scenario will happen only when a topgear user try to fill the link in the browser directly like this: https://topgear.topcoder.com/members/Rinal |
FYI, I have draft a challenge spec for this ticket, please take a look: |
@atif, please help with question 1 above. |
question 2. @LieutenantRoger, a scenario would be... |
Question 1: I found two challenges that allowing us to see a member handle. https://topgear.topcoder-dev.com/challenges/30055960?tab=registrants For this, it looks we need to find all areas on the topgear site where it shows a member's handle, this looks like a side task.
Question 2: The comment seems not complete. |
https://docs.google.com/document/d/1QEvbKQ9xPKqMZqWv_Fu9SQOMBQaWAAM39bpMj_yTDuc/edit?usp=sharing Here's a challenge spec to find all the URLs which contain member handle link under the |
Question 2: takes this challenge for example, https://topgear.topcoder.com/challenges/30118814, it's a public challenge but it's also made available on topgear. So if a topgear user goes into the registrant or submission tabs of that challenge and clicks on a public member's handle, it will take the user to the public domain. We want to change it so if it is a public handle, the topgear member should see below instead. |
I don't have access to above challenge. I think we need to setup a test challenge under topgear.topcoder-dev.com while we can use We will perhaps setup up more public handles in topgear domain in other areas (identified here: https://docs.google.com/document/d/1QEvbKQ9xPKqMZqWv_Fu9SQOMBQaWAAM39bpMj_yTDuc/edit?usp=sharing) to verify the navigation as well. |
@lakshmiathreya, can you help with the above? We need to set up a test challenge under topgear.topcoder-dev.com |
We need similar challenges in below private group as well in order to test the result: https://cs.topcoder-dev.com/challenges |
Is it possible a public member only can register a private group challenge ? It seems impossible given the current business logic as the private group challenge won't be visiable to public member. |
Please try to click the member-handles under this screen: https://topgear.topcoder-dev.com/challenges/30055646?tab=registrants https://topgear.topcoder-dev.com/members/tester1234 (Here is an example when a user is not having stats data). https://topgear.topcoder-dev.com/members/dan_developer (Here is another example when a user is having stats data). |
@LieutenantRoger, a public member cannot register for a private group challenge because it will not be visible on the public domain. |
Right , so topgear user under topgear domain won't able to click a public member to visit its profile, this will lead to point 2 above will never happen. So for a topgear user who does't have history data, could you check wheather this meet expectation above ? |
Could you please tell how a topgear user click on public member's handle ? In another word, will public members show up on |
all public challenges are visible on the topgear site so if a public member registers for a public challenge, a topgear user would be able to see the public user's handle in the topgear site. |
Ah, got it, that clarifies this. |
Does this look fine when a topgear user visit public member's profile screen ? |
That's correct. |
Tested the Fix.The Topgear user is still able to see the public member's handle details. I have also attached video for better clarity. |
@LieutenantRoger If we click the member handle from the member search results, it is directing to the member profile from the legacy page. Attached video for the same. |
Other than the above issue, everything is good Topgear page:
Topcoder page:
|
@SathyaJayabal It's environment issue, because the search page on dev environment is routing to legacy app, but the search in production page is still inside community-app. We are not using legacy search page in production, so we don't need to fix the legacy page. I guess @sushilshinde will have to update the search route on the dev environment to be served inside community-app as well. Here's a snapshot for comparison. |
@LieutenantRoger marking this as pass as per previous comment |
@LieutenantRoger please raise PR to develop |
Verified on dev env(develop branch) Topcoder pages: |
@LieutenantRoger @Oanh-and-only-Oanh Need clarification for the below. In the tco20 pages, |
I think this is expected behavior. tco20.topcoder.com can be treated as a sub-community as well, as it is for tco20 only. @Oanh-and-only-Oanh please comment more if you have otherwise opinion. :) |
Except the above clarification.Everything else is working fine. Topgear pages: Topcoder pages: |
@SathyaJayabal - why isnt this set to Pass? |
Uh oh!
There was an error while loading. Please reload this page.
1) Behavior: When a Topgear member clicks a member's handle, it navigates user to the public domain i.e. https://www.topcoder.com/members/RinalExpected behavior: When a Topgear member clicks a member's handle, user is navigated to the member's profile page WITHIN Topgear's domain. i.e. https://topgear.topcoder.com/members/Rinal2) If the member's handle is NOT part of Topgear's groupID, when a Topgear user clicks on a public member handle, this image and message should appear.

As we have discussed, we will implement this logic:
When we are under topgear domain, e.g. topgear.topcoder-dev.com, we then should open up a member's profile page in a new tab, (with the subdomain info retained in the url of the new browser tab)
When we are under public domain, e.g. www.topcoder-dev.com, we should retain the logic as is.
The updated requirement work will be done against
feature-private-navigation
The text was updated successfully, but these errors were encountered: