[resolved] Restrict Image Manager usage

[NikNak]

Hi

Is there a way to restrict the Image Manager access other than the 'modify files' preference?  I would like to keep the File Manager access but deny the Image Manager to my users.

The Image Manager really scares me, as it is all too easy for a user to delete an entire folder, or modify my carefully prepared image files with the editor. (I know they could still do damage with the file manager, but it is less likely imho)



Thanks

Nik

[Rolf]

Hi NikNak

You can use TinyMCE for this, look under profiles:

Restrict user's dir access:

"This will restrict the filemanagement-capabilities of the user to a subdir to 'uploads' which have the same name as the user's login. If the subdir does not exist, it will possibly be created. Please note, this currently only works with the standard dirnames, uploads/images. This may change in the future."

The user has its own folder and images on the server.
And hasn't access to the other folders.

Reg. Rolf

[NikNak]

Thanks Rolf

But it is the Content > Image Manager that is the issue rather than the placement of images from within TinyMCE.

The setting you mention only seems to affect the way the tinyMCE image insertion tool works, rather than the 'Image Manager'.

Kind regards

Nik

[Rolf]

True, but you can change the permissions for these users, that they don't have access to the Image Manager anymore...

[NikNak]

Thanks Rolf - I understand.

This indeed could be useful, but in my case I dont allow any user access to inserting images from TinyMCE, as they often mess it up - as seen on countless websites.

My wish was to be able to maintain the filemanager and hide the imagemanager in the backend, but I think this wont be possible without messing with the core. My reasoning was just to put the user a little more out of harms way, and the file manager just does a better job for what I want.

Not to worry - thanks

Nik

[Rolf]

My wish was to be able to maintain the filemanager and hide the imagemanager in the backend, but I think this wont be possible without messing with the core.

Indeed, the FileManager and ImageManager are combined in the same backend permission and can't be seperated...
Regards,
Rolf