-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Emtpy Templates folder is created even with 'templatedirectory' => '' #39227
Comments
The previous discussion was here: #27890 |
Confirming this bug. Note that if the configuration file contains only this line:
then the "Templates" folder is not being created.
then the empty "Templates" folder appears. Third case:
also the empty "Templates" folder is being created. |
cc @nextcloud/server-backend @juliushaertl |
This is part of the documentation
server/config/config.sample.php Lines 256 to 268 in 0d78334
|
I have created a feature request: #39266 |
Appreciated, however this looks more like a bug to me. Or is there any use to this folder? What if the skeleton folder contains a directory with the same name because somebody wants to ship file templates during account creation? |
The order of those two parameter seem to play a role.
Template folder is created.
Template folder is not created. |
It is highly unlikely that the order of the parameters in the array change anything. |
Bug description
Hi,
I'm using a custom skeleton folder. In my config file, I have:
When new users are created, they receive by default the files from the above skeleton folder.
But in addition, they receive also an empty folder called "Templates".
This "Templates" folder is not in my skeleton folder and the users should not have it by default.
I've tried all these options (with the same result):
Steps to reproduce
'templatedirectory' => '',
Expected behavior
The user should not see an empty "Templates" folder if
'templatedirectory' => '',
is set in the config file.Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
27
Operating system
RHEL/CentOS
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: