You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The optional custom logo that is on source and journalist interfaces is not preserved when the instance is upgraded from0.7.0 to 0.8.0. It is replaced with the default SecureDrop logo.
Steps to Reproduce
Install SecureDrop 0.7.0 in prod vms
Upload a custom Instance Logo
Upgrade to SecureDrop 0.8.0~rc1
Navigate to the Source interface and observe the default logo.
Expected Behavior
Upgrading to 0.8.0 should preserve the custom instance logo.
Actual Behavior
The custom logo is replaced by the default SecureDrop logo.
Comments
There are no apparmor/grsecurity errors, it seems like app code packaging/upgrade logic.
The custom logo is no longer found in /var/www/securedrop/static/i/
Workaround
Admin can run the install playbook to re-upload the image.
The text was updated successfully, but these errors were encountered:
This is due to an error on my part when building the debs: I had a local version of securedrop/static/i/custom_logo.png in the repo, which overrides the server version. Debs have been updated and I have confirmed the issue no longer persists.
Description
The optional custom logo that is on source and journalist interfaces is not preserved when the instance is upgraded from0.7.0 to 0.8.0. It is replaced with the default SecureDrop logo.
Steps to Reproduce
Expected Behavior
Upgrading to 0.8.0 should preserve the custom instance logo.
Actual Behavior
The custom logo is replaced by the default SecureDrop logo.
Comments
There are no apparmor/grsecurity errors, it seems like app code packaging/upgrade logic.
The custom logo is no longer found in
/var/www/securedrop/static/i/
Workaround
Admin can run the install playbook to re-upload the image.
The text was updated successfully, but these errors were encountered: