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
Issue after claiming full stack certificate - legacy full stack shows error #18253
Comments
This issue is a duplicate of #18128 The fix to this particular issue looks fairly simple - I think that removing lines 80-84 from I'm working on getting the app set up locally right now but hitting some roadblocks and may not have time to figure that out and make a PR for this. |
I would like to take a shot at this if anyone else has not taken it up yet? |
@nischaldutt give it a shot - @qualitymanifest that other issue seems to be two different issues in one, so I will leave this open for now, and if it gets fixed we can close this and post over there that the second problem is fixed - thanks for posting where the problem is |
@moT01 You're right, I should have said they are related, rather than calling it a duplicate. Better to address this issue individually. Thank you @nischaldutt for taking this |
I cannot find the specified file path |
Ah. That was from the After some searching of the current code, I can't find anything resembling the file I mentioned above, or anything that would cause this issue. However, the issue still persists on the live site, so I am under the assumption that the current |
Thanks for responding! I got it 👍 |
Okay, I think I finally get it now. It's pretty confusing with all these changes. After the repo overhaul, the I am not sure how often the current |
Is the problem still there @moT01 ? |
Yes @thecodingaviator, this problem still persists - you can see it by clicking the link to my profile I put in the issue description, then clicking the full stack cert under the legacy area. |
On a side note, when did you claim the Full Stack Certification? |
Okay, I've figured out the problem, we're using one and the same variable for the legacy and 2018 Full-Stack certs, this is somewhere messing up |
I believe #35608 will address this. |
@scissorsneedfoodtoo I guess so, I'll close my PR. @ahmadabdolsaheb I'm assigning you to the issue, please have a look |
I recently claimed my full stack certificate after having all the other certificates (including the 3 non full stack legacy ones) - When I claimed the cert, it showed up on my profile in two spots, the legacy area and the new area - so my profile looks like this...
I'm not sure if that's intentional or not but the issue is that when I try to open the legacy full stack cert it does not open and I get a flash message that looks like this...
The one at the top opens as expected
https://www.freecodecamp.org/mot01 <= my profile if you want to see the problem
The text was updated successfully, but these errors were encountered: