-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
File template rework #46455
Comments
To be evaluated additonally:
|
From discussion with @jancborchardt
Would be covered by the above
Can be handled by admin delegation
Could be done by an extra Templates folder for each collective/groupfolder but as a next step. |
Just talked about this a bit with @nimishavijay and there are 2 specific issues we came across:
|
Good stuff! Sounds like this work will effectively cover #38198 and #25358 (including most of the follow-on comments therein).
User-level templates would still be derived from a user owned/controlled folder in the proposed design. At the admin-level, they'd manage (upload/etc) templates via Admin settings. And users don't need to be able to edit the system provided templates.
I'm not sure how we'd handle folder specific templates, unless we started classifying folders... Wait, maybe we could associate templates with certain tags?... That would create the affiliation desired. Then the New button would activate for templates tagged the same as the folder the user is in. |
Can maybe take care of the #31414 transition at the same time we touch the user template folder settings. |
FYI @juliusknorr this concern of @nimishavijay and me was also seconded by @karlitschek and @schiessle – so having this as a folder which can be synced is a requirement. For this we need to keep in mind that the "Templates" folder name needs to be localized depending on language, which doesn’t work with a regular shared folder. |
…nfiguration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: nextcloud#39266 Related: nextcloud#46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl>
…nfiguration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl>
…nfiguration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl> Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
…in configuration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl> Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
…in configuration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl> Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
…in configuration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl> Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
…in configuration When both `skeletondirectory` and `templatedirectory` are set to empty strings in configuration, templates folder creation should be disabled and no Create templates folder option should be present in new folder menu. Related: #39266 Related: #46455 Author-Change-Id: IB#1156403 Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl> Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
Our current ways to manage, organize and distribute file templates is a wild mix of old code and not very accessible to admins and end users.
The server provides the possibility for a user defined directory but there is no option to change it or see which folder that is.
Additionally templates that we ship are only copied on user creation, so existing users will not get updated or new templates.
Collabora has additionally a separate config option for a user template directory and an admin Ui where admins can define instance wide templates:
Especially in larger organizations, defining and updating templates on the admin level is quite important, but also for us shipping new templates regularly this would be better way as currently those templates only reach new users.
My proposal to clean this up would be:
Open questions:
@nextcloud/designers for feedback
FYI @sorbaugh as it touches the area of files
The text was updated successfully, but these errors were encountered: