Set up a default public folder on contao:install command #712
Conversation
|
I would delete this folder on every installation. Why would I create just one public and one protected folder? I create folders for their content and usually publish them… If so, I would prefer a solution that folders are public by default like in Contao 3 (when added through the backend). |
|
No protected foder is created? Public folders are public recursively. So it makes a lot of sense to just put everything that should be public in one parent folder named |
|
I absolutely don't. I use folders like |
|
The point is that you need to provide the users with some folders and I think it makes sense to add a If you like to add a Anyway, I consider this to be best practice and I think it serves as a hint for administrators to see immediately that they have to make folders publicly available explicitly. That's why I want this to be part of the core. Let's see what others say. |
|
I am using a folder for each website-root as the first-level under files so i would probably delete public and protected after install. Why not put a readme.txt file into files? Sometimes the recursiveness bothers me but that was the case in contao 3 too where you could not place a public-folder inside a protected-folder. |
|
I found myself forgetting about the “protected by default” too, so +1 for the public folder. And for users that don’t want it, deleting a folder isn’t that much overhead I think. |
|
Personally I wouldn't want to use it this way, since it creates an additional level in the URL for any public files (in additional subfolders). Also just adding a Still, even then users just might assume it's the Generally I never liked that approach in Contao 4 all that much, since you can't simply have public files in the |
|
Can't we solve most of the issues if folders are just public by default? That's like 90% of the use case. Can't remember if we show that checkbox when creating a folder?
|
|
Yes, the checkbox is definitely there when creating a folder. |
Me too.
Yes, we could enable the checkbox by default.
I don't know if we should though? |
|
As discussed in Mumble on March 23rd, the "Public" checkbox should be checked by default. Also, it should be disabled in the subfolders of a public folder. |
|
Instead of checking and disabling the "Public" checkbox in the subfolders of a public folder can't we introduce something without that strict recursiveness? |
|
@asaage I don’t think that’s possible, because if a folder gets symlinked all subfolders are automatically public too. |
|
Implemented in b2b5a18. |
I think a lot of users forget that as of Contao 4, folders are protected by default.
And even if you know about it, I guess every project needs public files and I found myself creating the same file structure over and over again. I'm always using
While people might not like the "protected" folder, I think it is a good idea to create a "public" folder by default when setting up Contao. It makes setup faster and gives the users a hint about having to explicitly make folders public automatically.