When I hosted the original version of the project (the upstream). I didn't notice that code expects the prefix to be exactly 2 characters. this didn't cause problems at first because of the way the original version is hosted (see #3 for more details). After updating the hosting process, the following changes happened:
prefixes are now separated from the certificate id by a -.
prefixes are now generated automatically using 4 random characters.
The deprecation of the server-side rendering of the certificates, made the old certificates (created with v1) inaccessible.
There are two ways to fix this issue:
update the data in the database to include a - between the certificate id and the prefix
This won't work as the links written in the certificates are not updated
update the code logic to handle the cases of the certificates that were created before the update
When I hosted the original version of the project (the upstream). I didn't notice that code expects the prefix to be exactly 2 characters. this didn't cause problems at first because of the way the original version is hosted (see #3 for more details). After updating the hosting process, the following changes happened:
-.There are two ways to fix this issue:
update the data in the database to include a-between the certificate id and the prefix