What does "Make set Public" mean
Permalink 1 user found helpful
I looked around and can't seem to find an answer to what "Make set Public" means.
When uploading multiple files (after hitting "Start Uploads") you are directed to a new screen that has two tabs. ("Basic Properties", and "Sets") At the bottom of the sets tab there is a box you can check for "add to New set". After that there is a check box for "Make Set Public".
I was thinking that if the box (for "Make Set Public") was not checked that file could be displayed in a set but it would be more difficult for someone to download the picture, or that the images would not show to the public even if they were in an image block or slider block.
I did a test and uploaded multiple files (two separate uploads) and created one Private set and one Public set. I then went to one of the images in each set and looked at the properties to see where the files were stored.
Which looked something like this:
http://www.MySiteName.com/files/2000/2000/9000/imagename.jpg...
I logged into my C-Panel and went to the directory to see what the permissions were set to and in both cases they were set to 644. I was thinking that they would have been different but they were the same.
I also thought that this option for "Make Set Public" would determine if indexing was turned on or off for the set or folders where the images were stored, so that web bots would not crawl those directories.
So I tried going to the directory to see if I could view all the files in that directory
http://www.MySiteName.com/files/2000/2000/9000/...
and I also tried:
http://www.MySiteName.com/files/...
In both cases files and folders were not view able.
I checked the indexing settings in the control panel and they were set to "Default System Settings" , which I think means that the .htaccess file or php.ini file (I use a single php.ini file at root level opposed to a php.ini file under each directory or fastcgi)
So I am guessing the .htaccess file is restring indexing of those directories. There is an option in the cpanel for "(there is an option for "No Indexing" but if the .htaccess file is working I am not sure I need to change indexing from "Default System Settings".
I also added a Private set to a slider block, then logged out to see if the images would show in the slider for (public viewers) and I was able to see the private set.
So I was unable to figure out the what "Make Set Public" does or does not do for me.
Can someone help me understand the use of the "Make Set Public"?
Thanks
Albin
When uploading multiple files (after hitting "Start Uploads") you are directed to a new screen that has two tabs. ("Basic Properties", and "Sets") At the bottom of the sets tab there is a box you can check for "add to New set". After that there is a check box for "Make Set Public".
I was thinking that if the box (for "Make Set Public") was not checked that file could be displayed in a set but it would be more difficult for someone to download the picture, or that the images would not show to the public even if they were in an image block or slider block.
I did a test and uploaded multiple files (two separate uploads) and created one Private set and one Public set. I then went to one of the images in each set and looked at the properties to see where the files were stored.
Which looked something like this:
http://www.MySiteName.com/files/2000/2000/9000/imagename.jpg...
I logged into my C-Panel and went to the directory to see what the permissions were set to and in both cases they were set to 644. I was thinking that they would have been different but they were the same.
I also thought that this option for "Make Set Public" would determine if indexing was turned on or off for the set or folders where the images were stored, so that web bots would not crawl those directories.
So I tried going to the directory to see if I could view all the files in that directory
http://www.MySiteName.com/files/2000/2000/9000/...
and I also tried:
http://www.MySiteName.com/files/...
In both cases files and folders were not view able.
I checked the indexing settings in the control panel and they were set to "Default System Settings" , which I think means that the .htaccess file or php.ini file (I use a single php.ini file at root level opposed to a php.ini file under each directory or fastcgi)
So I am guessing the .htaccess file is restring indexing of those directories. There is an option in the cpanel for "(there is an option for "No Indexing" but if the .htaccess file is working I am not sure I need to change indexing from "Default System Settings".
I also added a Private set to a slider block, then logged out to see if the images would show in the slider for (public viewers) and I was able to see the private set.
So I was unable to figure out the what "Make Set Public" does or does not do for me.
Can someone help me understand the use of the "Make Set Public"?
Thanks
Albin
Thanks for taking the time to explain the purpose of the "Make Set Public". I Currently do not have others working on my sites, so it did not occur to me that it could be for internal privacy.
Its seems that the phrase is misleading, at least I think it is. If it is for internal use I would think "Make Set available to Group/s" would be more appropriate. (with all the groups listed and the ability to check boxes as to which groups, can or cannot see the set).
I also don't recall seeing where you could change an existing set from Public to Private, nor can you pick a Group and see what Sets they have access to.
I guess by the time I start to use this feature, it will be laid out a little different.
Thanks again.
Albin
Its seems that the phrase is misleading, at least I think it is. If it is for internal use I would think "Make Set available to Group/s" would be more appropriate. (with all the groups listed and the ability to check boxes as to which groups, can or cannot see the set).
I also don't recall seeing where you could change an existing set from Public to Private, nor can you pick a Group and see what Sets they have access to.
I guess by the time I start to use this feature, it will be laid out a little different.
Thanks again.
Albin
So, is there any way to manage sets via group permissions? Or are they only public/personal? I was hoping to implement a large site with multiple editors, and it sure would be nice if there were a way to segragate each editor's file assets by user-group membership.
If that's not built in, I'll probably be forced to code it in myself somehow.
If that's not built in, I'll probably be forced to code it in myself somehow.
Yes. You have to enable advanced permissions:
http://www.concrete5.org/documentation/how-tos/designers/using-adva...
But once you do that you can control which users and groups have access to sets of files. The permissions apply to all files in the set.
http://www.concrete5.org/documentation/how-tos/designers/using-adva...
But once you do that you can control which users and groups have access to sets of files. The permissions apply to all files in the set.
Is there an easy way to make a "Public" set "Non Public" ?
I've created my site relying heavily on images and am just now starting to add multiple users. I already have advanced permissions activated. The images are neatly arranged into several tens of sets, but they're all "Public" and the users have no business knowing about them.
From what I see in the interface, I'd need to create temporary sets for each set, move all the files over, re-create the set as non-public, and switch all the files back ... for each set ... yech (and error prone).
I'm not adverse to doing an update directly into the database, but I really don't know how safe that would be.
I've created my site relying heavily on images and am just now starting to add multiple users. I already have advanced permissions activated. The images are neatly arranged into several tens of sets, but they're all "Public" and the users have no business knowing about them.
From what I see in the interface, I'd need to create temporary sets for each set, move all the files over, re-create the set as non-public, and switch all the files back ... for each set ... yech (and error prone).
I'm not adverse to doing an update directly into the database, but I really don't know how safe that would be.
It comes into play when multiple people are logging into your site and it controls whether everyone sees the file set in the file manager or not.
For example, you might have some users of your site set up to only be able to edit certain parts of a site. When they open the file manager to add/choose resources, only sets that have been made public (and those they have created themselves) will be available.
In other words, by making a set public, you are choosing whether other users will have access to the set in the file manager.
For sites where you only have an admin user and that's it, it doesn't have any relevance.