This is probably a stupid question, but it's my first time here delving into the who user permissions phase of a site. I have a directory called images. Within that directory are several other directories used to categorize the images. If I grant access to this "images" directory, are the sub directories then automatically accessible. Or will have to assign access to every sub directory too?
I'm still working with my directory access issue and kind of came back at it from a different direction. I have a user with limited access, and I created the one directory called uploads. It's located at assets/uploads. I can see it and upload images to it as the super user, and my limited access user can do the same. So I thought, I want to put a folder within uploads for the client's logo (various formats — jpeg, ai, eps, pdf, etc. etc. ). So, as the super user, I created a new folder called logos, located at assests/uploads/logos.
So far so good, but my user cannot see that folder.
I can go to Media Source, and add the new media source and set the base path. This should give access to my user group. But does this mean that if the user wants to add a folder, they too need access to media sources and set a base path, etc. etc. ?
At the moment, my user only has permissions to create a file, not a folder. Maybe I should keep it that way for now. Just have them put all images and files into one folder and call it a day.
Just went I thought I was making progress, I feel more confused than ever.
My site is already built. I tend to put images into directories. The site is for a hotel, so it makes sense to me to put interiors images into folders associated with the corresponding room. So I have assets/images and then assets/images/rooms and then assets/images/rooms/room22, and so on. Do I have to set up each directory and subdirectory as a media source and set the base path and allow my user to access it?
Or, is there a quick way for me to just move all of those images into my other media source assets/uploads without disturbing the current paths that have already been established. As well, is there a way to do this without having to go into every resource and then re insert the images?
If they all have a common parent directory, you can point your media source at that, though it seems more sensible to put them under the assets/ directory since anonymous viewers should be able to see them.
Thanks Bob.
I think I am completely confused at the moment and need to step way back from it and review your book and the available permissions.
Assets is indeed the parent directory. However, it also contains the CSS & JS files, and some components items, which I don't want my user to see or be able to edit.
HOW I GOT HERE: I had followed a tutorial by Menno, creating a separate "uploads" directory for my "user with limited access" to put images. I think what the tutorial accomplished was to hide the entire assets directory from the file tree (protecting the css, js, and components items), but then make one directory — uploads — visible to the user with limited access. I created another folder within this uploads folder and it is not visible to my user with limited permissions. I assumed that since they could see the uploads folder, then they would also be able to see other folders within. Is there a permission that allows them to see sub directories? Maybe this is as simple as checking a box.
I hope I catch on to this permissions stuff soon!
directory_list
Yeah. My user can see the directory.
OK. So now, I think I probably just need to start the tedious task of just moving or copying the content type images from the images directory over to the uploads directory. That way, if my user removes a photo from a resource, they will be able to put it back, or put it somewhere on another resource.
Sounds like you've got it worked out.
