-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resource Manager - List view option, bulk actions and usability #4390
Comments
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. |
I would vote that this definitely needs to stay open and get fixed. |
I guess this issue doesn't get much traction as it is quite a lot. @donker would it be an idea to create several smaller items for this? |
If someone wants to split this up into more granular issue it would certainly help for management yeah. |
I'll take a crack at splitting this in to multiple issues... if a) no one else has started already and b) someone does a cleanup so its closer to standards after I am done hacking away. |
@valadas and @Tychodewaard - Okay, done for now. Maybe someone could spend a few minutes to verify that I didn't lose anything in the split? Happy to revise things further if needed. Cheers! |
@jeremy-farrance Thank you very much! |
@Valeria-B I think @jeremy-farrance did a great job splitting up this issue. I propose to close this one as it has all been accounted for in the issues mentioned. |
yes absolutely! |
Awesome, I did not have the time to read all the new issues and their comments but, smaller items are usually better :) Thanks for that splitting up effort. |
Description of problem
The current view of the folders and files in the new RM of DNN 9.8.0 is very difficult to visually navigate and manage. The actions are hidden (and not labeled, see #4384) and even relatively short file names are unnecessarily even more shortened, unless you hover on each one. Plus, every card is very bulky, so even a folder with a dozen files or little more becomes unnecessarily "long".
It doesn't help that files and folders have cards with the same background (and poor contrast with the text), and the image previews are mostly hidden (see screenshot 1).
Description of solution
Provide an option to switch to/set a more readable and compact list view, with already visible actions+labels, where the file/folder names are shortened only above 60-100 characters (or so) and the file type always visible.
Include a checkbox to select files/folders to perform actions, such as move and delete, on multiple files at once.
Ideally, the list view could also include "date added/last modified" columns.
Description of alternatives considered
Not ideal as a standalone alternative, but the "cards" view could also be improved by:
(see screenshot 2; it's just a quick edit via browser inspector, I know it's visually more busy and can be improved, but again, I still consider the list view option much better)
Screenshots
Screenshot 1 (current view)
Screenshot 2 (modified view)
Additional context
A use case where all of this becomes a serious hindrance: a content editor, who needs to regularly upload and manage a significant amount of pictures or other files. They might need it for sharing or to perform regular massive content uploads/updates in another extension (eg. news articles or e-commerce catalogs). They realize they erroneously uploaded 100+ files, but all the jpegs should have gone into another folder, others should be deleted and a few should stay where they are. All the file names start with a similar string with an identifier at the end. All the previews look very similar. The editor now has to hover over each box to verify what file it is and perform the appropriate action one by one.
Affected browser
Doesn't seem to be a browser-related issue
The text was updated successfully, but these errors were encountered: