Bug: User with only ability to move files unable to see check boxes to move multiple files.

[Dazz]

Not sure if this has been reported or if this is working as designed or not...  

I don't use a "moderators" group. I give individual users various permissions to perform various tasks. MY goal is to give one of my users permissions to ONLY move files within my Files sections.  The user can move files one at a time, but they don't see how to select multiple files to move.

User is given ONLY option to Move content.  

 

This gives the user the option in file view for move the file:

 

However this does not give the user any boxes so they can select multiple files to move. 

 

If you give that user ALL permissions for the "Content" tab

 

This does show the user the boxes to move multiple files. The Check boxes now appear.

 

Is there something else that I need to assign to the user to allow them the ability to move multiple files without giving theme all permissions (as they don't need it for this task). Or is this a bug?

 

[Adriano Faria]

6 minutes ago, Dazz said:

MY goal is to give one of my users permissions to ONLY move files within my Files sections.

Then disable the move where you show and enable it in the Downloads tab.

[Dazz]

4 minutes ago, Adriano Faria said:

Then disable the move where you show and enable it in the Downloads tab.

It is enabled there as well.
 

[Adriano Faria]

12 minutes ago, Dazz said:

The user can move files one at a time, but they don't see how to select multiple files to move.

Sorry, didn't read this.

16 minutes ago, Dazz said:

If you give that user ALL permissions for the "Content" tab

 

16 minutes ago, Dazz said:

This does show the user the boxes to move multiple files. The Check boxes now appear.

I can confirm it too. It's a bug.

[Marc Stridgen]

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

[Dazz]

On 7/28/2023 at 9:17 AM, Marc Stridgen said:

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

Any update on fix for this bug?

[Marc Stridgen]

This is showing as a resolved issue in our bug tracker, so you should see this in the next release

[Marc Stridgen]

This issue has been resolved in our recent 4.7.14 release of the platform. Please upgrade to resolve the issue, and if you see any further problems at that point, please let us know.