silverstripe-cms
silverstripe-cms copied to clipboard
silverstripe
Insert media file upload defaults to /Uploads folder, no way to change it in options
Once you upload a file, there should be a way to specify which folder the file should upload to, rather then forcing all files should go in the Uploads folder by default.
It is really annoying to upload a number of files and then have to move them into the specific folders manually.
Yes, this is an annoying issue. A good thing to bring up for 3.2. Maybe we can implement another option in the insert dialogue?
The problem is that currently the upload folder is set by code, not by the user. It's an extension that even the built in UploadField lacks.
With the media dialogue, there isn't even a way to do that on an editor-by-editor basis, because currently you can only change the global editor config. There has been some work recently towards allowing more customisability of different editors, so the ability to specify upload folders for different pages could be close. It still doesn't let the user select it, only in code though. :)
@tractorcow would this module sort this issue? https://github.com/silverstripe-labs/silverstripe-selectupload
Yes it would. :) Who wrote that glorious module anyway?
Are you happy to close this ticket?
From the perspective of a heavy user and the person who gets blamed for the interface oddities and inconsistencies in SilverStripe, this isn't a "nice to have." It's a necessity. UX eccentricies like this nibble away at my organization's support for SilverStripe. It's by no means a widespread CMS here in the US. Yes, yes, I understand it's more than a CMS...but the people who find they can file images from one view but NOT from another don't care if it's more. They care if it offers them a consistent user experience. So. Please. Include in 3.2. Please. I don't want to give any more ammunition to the "We need Wordpress!" crowd.
My feeling says that it's probably too late to add new ideas for 3.2, but I'm going to flag this as a possible new feature for 3.3, even if it's a simple move of the external module into core.
Thank you! We just added the module and it works well, but really having a consistent UX should be core. :)
There are designs which cater to this experience (including other enhancements) but they are not developed yet. Check them out here https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/asset/components/5b5e6e3984472000117f3ee4
Same issue https://github.com/silverstripe/silverstripe-asset-admin/issues/759
~~### New Potential designs https://invis.io/WCMZMHHXRJV#/381953634_Files_Tiny_Insert_Files_new_File_start https://invis.io/WCMZMHHXRJV#/381953633_Files_Tiny_Insert_Files_existing_File_start~~
~~Comments on any edge cases are welcomed~~
There are designs which cater to this experience (including other enhancements) but they are not developed yet. Check them out here https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/asset/components/5b5e6e3984472000117f3ee4
@clarkepaul I'm commenting really late so don't know if these designs are up to date but I'm going to leave some feedback for what it's worth! I like how you've used the term 'File manager' - that's much better than 'Files' IMO because it's more clearly referring to a CMS section and helps reduce ambiguity. Can we standardise on that and not call it 'Files' anywhere? I notice in the same designs there is a 'View in Files' reference which is inconsistent terminology. I'd also prefer 'Browse' to say 'Upload' as per recent changes
@jonom That's what I was trying to do with calling it a File Manager so that's good! The main change was swapping the order of the links (people instinctively click on the first link thinking its the CMS files). With the design inconsistencies, it's hard to keep everything up-to-date but we do try to maintain the latest concepts—usually things like that get fixed up once it is prioritized and groomed for development. Otherwise there's a mix of new and really old designs in there (not enough hands to keep it all up-to-date :( . The wording change hasn't been discussed widely as yet, but your the second person to have picked up on it with positive reactions.
The change in text from Browse to Upload went under my radar unfortunately, I only noticed it last week. I think this would have been less of an issue with my proposed designs but Upload should make it even clearer. Added "Upload" to designs FYI.
The proposed functionality in this issue and in https://github.com/silverstripe/silverstripe-asset-admin/issues/759 will probably make the SS4 version of this module silverstripe/selectupload redundant.
When the fix is made and merged, let's maybe re-evaluate the use case for silverstripe/selectupload and potentially deprecate the SS4 branch.
