When a course certificate is in Activated state in OpenEdX Studio, the Delete (trash) icon remains visible and clickable on the certificate card. Clicking it triggers an on-screen error. Since the backend already blocks deletion of active certificates, this is a frontend-only guard issue — the Delete icon must be hidden when the certificate is activated.
Steps to Reproduce
Log in to OpenEdX Studio as a Course Author or Studio Admin.
Navigate to a course → Settings → Certificates.
Create a new certificate and configure it.
Activate the certificate (toggle to Activated state).
Observe the certificate card — the Delete icon is still visible.
Click the Delete icon.
Observe the on-screen error.
Expected Behavior
Delete icon is not visible when the certificate is in Activated state. If deletion is needed, the user must first deactivate the certificate.
Actual Behavior
Delete icon is visible on an activated certificate. Clicking it throws an on-screen error because the backend rejects the request.
Note: user role should be admin not superr user
When a course certificate is in Activated state in OpenEdX Studio, the Delete (trash) icon remains visible and clickable on the certificate card. Clicking it triggers an on-screen error. Since the backend already blocks deletion of active certificates, this is a frontend-only guard issue — the Delete icon must be hidden when the certificate is activated.
Steps to Reproduce
Log in to OpenEdX Studio as a Course Author or Studio Admin.
Navigate to a course → Settings → Certificates.
Create a new certificate and configure it.
Activate the certificate (toggle to Activated state).
Observe the certificate card — the Delete icon is still visible.
Click the Delete icon.
Observe the on-screen error.
Expected Behavior
Delete icon is not visible when the certificate is in Activated state. If deletion is needed, the user must first deactivate the certificate.
Actual Behavior
Delete icon is visible on an activated certificate. Clicking it throws an on-screen error because the backend rejects the request.
Note: user role should be admin not superr user