File sets: my sets - public sets
Permalink
I wonder how i could change the typ of a file set, from "My Set" to "Public" and vice versa, (for instance, if i had forgotten to make it public while i created it after uploading files to it)? If i go to Files - File Sets, i can only rename or delete a set. It would be nice to have a checkbox to define a set as "My Set" or "Public".
There is some inconsistency:
1) If i create a file set by clicking the button File Sets - Add File Set, i will not be asked if i want to create it as "Public" or "My Set" set, it's always public.
2) If i create a file set right after uploading files, forgetting to check the checkbox "Make File Set public", it's private. So here it's private as default.
It would be nice to have the choice of file set types in both cases, and also to be able to change the type of existing file sets.
There is some inconsistency:
1) If i create a file set by clicking the button File Sets - Add File Set, i will not be asked if i want to create it as "Public" or "My Set" set, it's always public.
2) If i create a file set right after uploading files, forgetting to check the checkbox "Make File Set public", it's private. So here it's private as default.
It would be nice to have the choice of file set types in both cases, and also to be able to change the type of existing file sets.
Does anyone know how i could change a set from "My Set" to "Public"?
I checked and did not see a way to switch a set from My Sets to Public after the set is created.
I recommend going through the GitHub issues and seeing if there is an issue for it (in both closed and open issues).
If there isn't an issue for this, you could post one requesting the feature.
https://github.com/concrete5/concrete5/issues...
I recommend going through the GitHub issues and seeing if there is an issue for it (in both closed and open issues).
If there isn't an issue for this, you could post one requesting the feature.
https://github.com/concrete5/concrete5/issues...
Did this issue get resolved? I would like this functionality also.
I had a look on Git as Dilkington suggested and foundhttps://github.com/concrete5/concrete5/issues/2302... the issue was closed but I can't tell if it was resolved or not. (not really savvy with github)
I had a look on Git as Dilkington suggested and foundhttps://github.com/concrete5/concrete5/issues/2302... the issue was closed but I can't tell if it was resolved or not. (not really savvy with github)
@gavthompson
I checked again and don't see an option to switch file sets from Public to My Set and back. The GitHub fix may have been for something else
I checked again and don't see an option to switch file sets from Public to My Set and back. The GitHub fix may have been for something else
Since it hasn't changed, i just opened an issue for this in GitHub.
https://github.com/concrete5/concrete5/issues/2597...
https://github.com/concrete5/concrete5/issues/2597...
Good Stuff Okapi, seems like such an elementary option to have, would be a shame for it to be over looked.
In this context I had a problem as well - there is no possibility to give admin or super admin access to private file sets. If you have to handle a huge amount of users (in my case teachers at a school) it should be possible to "clean up" the file sets and the files inside.
As well it should be possible to specify a special file set for every user / group.
As well it should be possible to specify a special file set for every user / group.
Besides, as far as i see, custom permissions, enabled for filesets, seem to not override "private/public".
For instance, if admin 1 has created a private fileset with custom permissions enabled where full access is defined for the administrators group, it's still not accessible to other admins.
This is confusing...
For instance, if admin 1 has created a private fileset with custom permissions enabled where full access is defined for the administrators group, it's still not accessible to other admins.
This is confusing...
Hello,
Here is how I managed to change a private file set to public file set using Concrete 5.7.5.6, use at your own risk, DO database backup before everything else and test-test-test (even if I have not noticed any issue so far) :
- Access your website database with PhpMyAdmin or any other method,
- go to table "FileSets" which contains your file sets,
- you need to change the "fsType" field for each file set you want to make public or private, put "0" for private file set and "1" for public file set.
I hope it helps.
Here is how I managed to change a private file set to public file set using Concrete 5.7.5.6, use at your own risk, DO database backup before everything else and test-test-test (even if I have not noticed any issue so far) :
- Access your website database with PhpMyAdmin or any other method,
- go to table "FileSets" which contains your file sets,
- you need to change the "fsType" field for each file set you want to make public or private, put "0" for private file set and "1" for public file set.
I hope it helps.
This is Andrew's response at GitHub:
"Changing a file set from private to public isn't really feasible – private sets are completely for organization and public sets can have permissions on them.
The checkbox could probably stand to be checked by default, so that file sets are public by default. File sets created through the Dashboard are always public.
If you accidentally create a set of the wrong type, just delete it and re-create it."
Current state of the issue: closed.
"Changing a file set from private to public isn't really feasible – private sets are completely for organization and public sets can have permissions on them.
The checkbox could probably stand to be checked by default, so that file sets are public by default. File sets created through the Dashboard are always public.
If you accidentally create a set of the wrong type, just delete it and re-create it."
Current state of the issue: closed.
Shame shame.
IMO, public by default has got to be the logical approach. Make the tick box "my set" instead.
IMO, public by default has got to be the logical approach. Make the tick box "my set" instead.
Totally agreed.
"The checkbox could probably stand to be checked by default" doesn't sound like this is going to get resolved soon.
"The checkbox could probably stand to be checked by default" doesn't sound like this is going to get resolved soon.
