View Issue Details

IDProjectCategoryView StatusLast Update
2768Composrfiledumppublic2018-02-07 16:55
ReporterPDStig Assigned ToChris Graham  
PrioritynormalSeverityfeature 
Status closedResolutionduplicate 
Summary2768: Make the filedump more intuitive
DescriptionThe filedump is already pretty intuitive as it is. But based off of reviewing other CMS systems, I feel the filedump has more potential than what we use it for.

1. The filedump could be an excellent media container / library for when content is embedded into pages and posts. Replace the attachment system with filedump... all attachments are stored in a special spot in the filedump (perhaps it auto-creates folders depending on where the attachment exists), allowing for easy and global administration of all embedded content on site. This eliminates the need to have to use separate "attachment managers"... all media is centralized in the filedump.

2. In addition to 1, allow the filedump to host all uploads to the website for the same reasons presented in 1.

3. Build drag-and-drop functionality for the filedump so that users can drag and drop files to their web browser to upload. Perhaps make this a screen that is also shared among upload fields and not just the filedump. Offer our current uploading functionality (click and browse) as a fallback.

4. Enable cropping support for image uploads (see related issue).

5. Re-work the interface for selecting an already-uploaded filedump file as a file for image/file fields in a form. Instead of using an expand/contract list, have a filedump interface pop up as an overlay and allow the user to browse for the file they want via. filedump. This would allow the user to preview files (especially images) before selecting one... and gives them the navigation functionality of the filedump.

6. Enable permissions on a per-folder basis for the filedump. Allow staff to be able to set who can view certain folders and the content within that folder, who can use the files in the folder on forms, who can upload files in that folder, who can create new folders inside, and who can edit/delete own/any files within that folder. View permissions for top-level folders would override permissions for subfolders (aka. if a top level folder restricts view permissions for X usergroup, then X usergroup cannot access any subfolders either regardless of their individual view settings).
Additional InformationFeel free to break this up into multiple tasks.
TagsNo tags attached.
Attach Tags
Time estimation (hours)
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Relationships

related to 1500 ClosedChris Graham Filedump integration with ckeditor and add-block 
related to 1511 ClosedPDStig Option to upload to the library, instead of attachments 
related to 1881 ResolvedChris Graham Allow upload/URL combo widget to also take from filedump 
related to 1982 Not AssignedGuest Cropping tool 

Activities

Chris Graham

2016-08-11 20:31

administrator   ~4229

This issue needs separating out... some of the issues you already linked to, so any expansion or discussion should be solely under those issues. Other things which standalone should be in their own issues, e.g. filedump permissions wouldn't be dependent on, or have a dependency from, the other parts of this.

Individual issues can then be thought about more easily, and individually sponsored.

Issue History

Date Modified Username Field Change
2016-08-11 18:05 PDStig New Issue
2016-08-11 18:05 PDStig Relationship added related to 1500
2016-08-11 18:06 PDStig Relationship added related to 1511
2016-08-11 18:06 PDStig Relationship added related to 1881
2016-08-11 18:06 PDStig Relationship added related to 1982
2016-08-11 18:10 PDStig Description Updated
2016-08-11 20:31 Chris Graham Note Added: 0004229
2016-08-11 20:31 Chris Graham Status Not Assigned => Closed
2016-08-11 20:31 Chris Graham Assigned To => Chris Graham
2016-08-11 20:31 Chris Graham Resolution open => suspended
2018-02-07 16:55 Chris Graham Resolution suspended => duplicate