[MGNLUI-8425] Import as yaml fails on Windows Created: 06/Oct/23 Updated: 27/Nov/23 Resolved: 14/Nov/23 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.39 |
| Fix Version/s: | 6.3.0, 6.2.41 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Adam Siska |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 0.5h | Time Spent: | 0.5h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||
| Template: | |||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||
| Work Started: | |||||||||||||||||||||||||
| Approved: |
Yes
|
||||||||||||||||||||||||
| Description |
Steps to reproduce
Expected resultsThe page can be imported Actual resultsThe upload is aborted and the message "An unsupported upload file type" is displayed Workaround
Development notesWhen removing the allowedMimeTypePattern restriction from the dialog we found the upload to detect the file as application/octet-stream |
| Comments |
| Comment by Richard Gange [ 06/Nov/23 ] |
|
I think one option here is to have a fallback mechanism based on the extension. We do have the mime mapping registry /server/MIMEMapping/x-yaml@extension. However it does seem like a bug within the upload field itself. |