Thread

No - Not all files but just those that would need it - images and PDFs - so that’s not it.

One other note-Image previews are placed in the form once selected, but aren’t visible in the file browser. But perhaps we can follow this up in a support channel..

I’ve had that same issue - clients just not paying attention and what-hey?  The file comes out on the site just fine so they never see it as an issue.

Seems like I can recall a FR from years ago that would allow us to assign a per-channel default file upload, and now with the file field type to make it a configuration at that level.

A catch-all default would be good too.

I would like to add my vote for a channel default upload directory, similar to what you get with Wygwam.

Roi

A bit late to the party but here are my 2 cents:

Nice first shot at the file manager and having such betas coming our way is great! The thumbnails / filename dual view is a nice improvement IMHO.

To summarize what I would like to see in regards to the File Manager:

* Agree that some (most) clients mess it up when they can choose an upload location. At least being able to assign a default would be really nice. Better if we can choose to tie one upload location to a file field and lock it. I like the safecracker file approach but having all existing files into a drop down is problematic UI wise. Now that it’s part of the product, maybe it’s possible to tie it to the File Manager.
* Being able to do batch uploads via the file manager tab (not the publish page) would be great. Auto-deflating .zip files would be a great start.
* A quick and easy way to regenerate thumbnails for files uploaded via FTP (or for files migrated from EE 1). Currently, a home-baked script is the only way since thumbs are just generated during upload.
* Since we now have a table view, can we get column sorting in the file manager as well ;o)

Keep on the good work!

+1 for jeromecoupe’s feature requests (couldn’t have summarized it better, I demoed EE2.1.4 and this is exactly what site owners need)

Of all the presentations I did, I never got a question from customers to create or manage file uploads in subdirectories. But batch uploading and large file uploading almost always came up.

+1 for jeromecoupe’s feature requests (couldn’t have summarized it better, I demoed EE2.1.4 and this is exactly what site owners need)

Of all the presentations I did, I never got a question from customers to create or manage file uploads in subdirectories. But batch uploading and large file uploading almost always came up.

I think it certainly depends on the market segment you’re working in - my clients generally do news sites, large ones at that. Its all well and good to say “clients only ruin things”, but ultimately it’s the client’s site and you can only give them a good start. Some clients needto be managed and something of a safety net, and others are savvy enough to be let free to do their own thing. Often your work takes on a new life; giving them the flexibility to explore options is important, and with any luck they’ll call you back to do “enhancements”, not “fixes”...

Basically it’s not enough have to choose between one solution or another - it’d be great to have both default folder for some groups and an open system for high-level groups. We need both.

I’ve worked for the two largest news organizations in the Netherlands, and the primitive native file manager made them question the power and flexibility of the platform. “If they can’t get this right, what else is lurking inside?” is the generalized response..completely unfair, but I also can’t say I don’t get what they mean…this should be core functionality, not a plug-in that can break later. They’re time-sensitive and change-phobic, but not stupid.

Hi there Jim,

As you said, not all clients ruin things. Maybe I didn’t express myself clearly enough. What I mean is that it would be nice to have the choice between locking an upload pref to a file field (for less savvy clients) and leave the choice to more savvy ones.

Hi there Jim,

As you said, not all clients ruin things. Maybe I didn’t express myself clearly enough. What I mean is that it would be nice to have the choice between locking an upload pref to a file field (for less savvy clients) and leave the choice to more savvy ones.

Completely agree - this should be something tuned to the member access level, based on their member access level (extending the channel posting privs we have now) - what I’d ideally like would be:

• Admins and Senior Editors: have full access; add, delete scale and edit, on files. They’d be able to through subdirectories in the Images directory. Should be able to make new directories from the UI (eg: 2011 dir, with Jan, Feb, Mar subdirs, and so on). Batching would be bitchen…

• Editors could just see into the system, add to any directory and place images into articles

• Users could see only 1 directory and place images.

This makes everyone happy.