Freecodecamp: Legacy Certificates Not Labelled As Legacy

[nhcarrigan]

Describe 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:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. 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.

[ojeytonwilliams]

Hey @nhcarrigan thanks for bringing this up. As for the URLs, they're not supposed to change. The intention is that people can link to them from outside and rely on those links continuing to point to their certificates.

Once you have the newer one it should have a unique link (and not have the word legacy in it!).

[dboydgit]

Is there an issue here? Was going to work on it, but not sure what the issue is.

[scissorsneedfoodtoo]

Hi @nhcarrigan, thanks for catching this.

If I remember correctly, leaving the slug as /information-security-and-quality-assurance was a conscious decision so links to already claimed certificates don't break as @ojeytonwilliams mentioned. While we did change the URLs to other certificates in the past, we have to manage those redirects manually.

The new certificates have different names/versioned slugs (/information-security-v7). Going forward, the plan is to use the versioned slugs to determine whether a certificate is legacy or not. For instance, if we make a change to the information security certificate, /information-security-v7 will have the legacy header like in your screenshots, and /information-security-v8 will be the current one.

I think we can probably close this issue if all the new certificates behave the same way.

[nhcarrigan]

I ran into no issues when testing the certificates on the local instance with the development user. 🙂

[scissorsneedfoodtoo]

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.