Dnn.Platform
Dnn.Platform copied to clipboard
dnnsoftware
File suffix with Resource Manager in 9.8.0
I am populating a brand new install of 9.8.0 with the Telerik components removed.
I needed to upload a number of images from my client of various sorts (png and jpg). THe filenames had extensions mostly in lower case but 3 images were labelled with .JPG. The Resource Manager refused to upload these.
I went to the allowed file types and added JPG as one of these and retried - again the file were rejected.
Finally I change the filenames extensions to lowercase jpg and the files were accepted and uploaded with no problem.
I am attaching two versions of one of these files in both variants to see if others have this issue.
Upper case file name extensions are so very, very, very wrong. Can we call this a feature?
I do agree with the sentiment. It is just what came from the client.
If most people agree it should stay as it is then I am good with that. Perhaps this should be more widely known. Maybe it is expect for me.
Regards
Simon Thompson From: Jeremy Farrance [email protected] Sent: 27 November 2020 16:05 To: dnnsoftware/Dnn.Platform [email protected] Cc: Simon Thompson [email protected]; Author [email protected] Subject: Re: [dnnsoftware/Dnn.Platform] File suffix with Resource Manager in 9.8.0 (#4338)
Upper case file name extensions are so very, very, very wrong. Can we call this a feature?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/dnnsoftware/Dnn.Platform/issues/4338#issuecomment-734899165, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANN6ZPIWNIHZXJACJ723URLSR7E33ANCNFSM4UEY7QFA.
Yeah, sorry, I was being glib. In the real world my mild OCD doesn't matter, technically extensions can be upper case. An option in the file manager to auto-lower-case them on upload would be nice, but again, my mild OCD.
IMHO, by default, the resource manager should allow upper case extensions.
Jeremy, I would agree with your suggestion as a fellow mild “CDO” sufferer.
Simon Thompson From: Jeremy Farrance [email protected] Sent: 27 November 2020 16:15 To: dnnsoftware/Dnn.Platform [email protected] Cc: Simon Thompson [email protected]; Author [email protected] Subject: Re: [dnnsoftware/Dnn.Platform] File suffix with Resource Manager in 9.8.0 (#4338)
Yeah, sorry, I was being glib. In the real world my mild OCD doesn't matter, technically extensions can be upper case. An option in the file manager to auto-lower-case them on upload would be nice, but again, my mild OCD.
IMHO, by default, the resource manager should allow upper case extensions.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/dnnsoftware/Dnn.Platform/issues/4338#issuecomment-734902983, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANN6ZPMBQLDANFVPOHAGWJLSR7GAXANCNFSM4UEY7QFA.
Thanks for reporting this. Hopefully, it's a simple fix. I'll take a look into this as soon as I have some available time to do so.
@simont1952, thank you for putting the letters in order. Much appreciated!!
@simont1952 I finally got a chance to look into this further and it appears the issue is not in the Resource Manager module, but rather in the DNN internal service that it uses. I was not able to pinpoint the exact issue before running out of time.
That said, there is a serious effort going on to replace this solution altogether with a new file manager. So, I really don't want to spend too much time on tracking this one down when it is going to be replaced soon anyway.
@david-poindexter This issue is WITH the new file manager, so we need to make sure that we validate that this goes away with the work-in-progress updates
@simont1952 @jeremy-farrance @mitchelsellers - @valadas and I have verified this is working correctly in the new Resource Manager (to be included in the 9.11.0 release of DNN). We'll go ahead and close this issue, but we recommend testing this in the forthcoming release candidate. If you still experience issues, please respond to this issue and we'll happily reopen it. Thanks!