Separate manager access to uploaded files

I have several sections in my site and each group of managers is responsible for editing documents in particular section. I want to separate also files, uploaded by each manager using FCKEditor (don’t allow one manager affect other’s pictures).
Maybe create special directory for each document/manager...

I think I’m not the first having this problem. How solved you this problem?

In each user’s User tab you can set the resource path.

Yes, susan you are right but it doesnt apply when you use RTE and mcpuk, only if you use the backend file manager...

i need this feature too ... so hard to be a php newbie in the modx world...

I confirm the mentioned issue. I think that there may be an issue since when you set the resource path for the individual user the site breaks since it looks for plugins/snippets in the user defined resources as well as the MCPUK resources. It seems to me that this should only effect the MCPUK resources and not the entire sites resources (otherwise you would need copies of your plugins/modules/snippets in every user defined path as well.

But I may be doing something wrong

I posted regarding this issue recently but did not get any replies and ended up forgetting about it (or at least postponing my concern): http://modxcms.com/forums/index.php/topic,23196.msg143053.html#msg143053

hey dev_cw ! i just try to copy these folders (snippets/plugins/images/files) into the "user" folder.

then i changed the two fields relative to MCPUK ressources (one from root and the relative one).

...and it works !

the biggest problem here is that there is a lot of redundancy in this process... ~1000 files per user.. and i have 54 manager users.. :’(

maybe there is a little bug here.

The File Manager (Resources -> Manage Files) is NOT the Resource Browser (MCPUK). I found this out the hard way as well when I started programming my snippets to use [tt]$rb_base_path[/tt] (rb = Resource Browser) instead of the proper [tt]$base_path.’assets/’[/tt].

MODx does not control where snippets look for their external resources, so some of them use [tt]$rb_base_path[/tt] while others use [tt]$base_path.’assets/’[/tt]. In a default environment both will work and in fact point to the same location on the filesystem. It’s only when folders have been moved around and settings modified that those start to report different locations.

What you’re experiencing is a bug in the snippets and most likely not with the MODx core. The only "bug" in this scenario is that MODx is too flexible.

I have a similar scenario, and I solved it by changing both the File Manager path AND Resource Path for the specific users. However, I have the luxury of knowing enough PHP to fix the snippets that are programmed to use the incorrect [tt]$rb_base_path[/tt]... :-/

I see what you are saying. I see many snippets using $rb_base_path and was always puzzled since I had never heard or seen this var in the documentation. I will check this out. Thanks.

Too much freedom can cause all sorts of problems.

EDIT: I just tested this and by golly it works.

i confirm that changing $rb_base_path with $base_path.’assets/’ solve the problem. Many thanx !