-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export Wizard bombs out on some project images #2562
Comments
Aware of http://help.octopusdeploy.com/discussions/problems/44107 and #2324 - I guess when uploading there should be some validation on what's actually being uploaded - I have no idea how someone managed to upload an xml image |
SVG is also an issue |
.ICO apparently also an issue |
Fixed |
We have had several issues recently where a certain MimeType was not understood by the migrator:
When exporting data from an Octopus instance where something has a logo using an "unsupported" MimeType the exporter will fail. Similarly the import was depending on knowing how to convert file extensions back into a MimeType. We don't need MimeType during export/importAfter investigating this all the way through I've discovered we really don't need this conversion at all during export/import: the "owner" of the Logo actually contains our best knowledge of the MimeType because it is calculated when the Logo is first uploaded: https://github.com/OctopusDeploy/OctopusDeploy/blob/master/source/Octopus.Server/Web/Api/Actions/BaseLogoPutResponder.cs#L57 This means we can safely remove all of this brittle code and just let the logo files go back to being a |
Release Note: Data migration (export/import) no longer cares about the MimeType of logos |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately. |
It seems you can upload multitudes of possible images for Project Icons. When running the export wizard it will bomb out due to MimeTyping.
One example -
And another example;
The text was updated successfully, but these errors were encountered: