Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Legacy Certificates Not Labelled As Legacy
See original GitHub issueDescribe the bug With the first wave of v7 going live, the Information Security and Full Stack certificates have correctly moved to a “Legacy” header. The certificates, themselves, have not been labelled as “legacy”, however.
To Reproduce Steps to reproduce the behavior:
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior
The Legacy certificates should probably say “Legacy” on them, and the URL should be updated from https://www.freecodecamp.org/certification/nhcarrigan/information-security-and-quality-assurance to https://www.freecodecamp.org/certification/nhcarrigan/legacy-information-security-and-quality-assurance, as an example, to prevent possible conflict with the new certificates.
Screenshots
Desktop (please complete the following information):
- OS: Windows 10 v. 1909
- Browser: Chrome
- Version: 83.0.4103.116
Additional Context I will update this issue after I’ve claimed the new information security certificate to see how that behaviour is implemented.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Awesome, thanks for confirming that @nhcarrigan. I’ll close this for now, but please feel free to reopen it if you notice anything else that we missed earlier.
I ran into no issues when testing the certificates on the local instance with the development user. 🙂