Assuming I don't want my clients editing media - they're going to expect this allows them to edit the image itself, not just change the displayed name, and I don't want them even thinking about that just yet - how about providing a UI option to disable this functionality and remove the "edit" button?

Comments

johnpitcairn’s picture

Status: Active » Closed (works as designed)

I'm embarrassed ... found the permission under File Entity. Apologies for the noise.

johnpitcairn’s picture

Title: Provide option to disable editing media » Provide option to disable editing media without disabling file upload
Status: Closed (works as designed) » Active

Re-opening.

To disable the media "edit" buttons I need to disallow the file entity "edit file" permission.

This has the unwanted side-effect of also preventing file uploads.

darksnow’s picture

Status: Closed (duplicate) » Active

I'm a bit confused about these permissions too.

In order to allow my users to upload images to the media library I have to give them "Edit Media" permissions. The permission that looks correct, "Import media files from the local filesystem", doesn't seem to have any affect.

I also can't find any permissions at all for "File Entity".

Am I missing something or does something need changed?

Cheers.

dave reid’s picture

Status: Active » Closed (duplicate)

This is a duplicate of #1227706: Add a file entity access API which will have separate permissions for 'create files', 'edit own files' and 'edit any files'. Right now without that patch it's possible by adding in a process callback to the media element info to disable the edit button. Or you could just hide the button with CSS.

darksnow’s picture

Status: Active » Closed (duplicate)

Thanks Dave.

Can you clarify what "Import media files from the local filesystem" does?

johnpitcairn’s picture

Or you could just hide the button with CSS.

Yeah, that's what I'm doing until things become more configurable, I'm not keen to track another modification just for this. Thanks for the info.