| Server IP : 93.86.61.54 / Your IP : 216.73.216.60 Web Server : Apache/2.4.62 (Ubuntu) System : Linux rasin.ddns.net 6.8.0-124-generic #124~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 21:05:19 UTC x86_64 User : www-data ( 33) PHP Version : 8.4.22 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /var/www/html/projects/nextcloud/apps/richdocuments/docs/ |
Upload File : |
# Templates Often users will use the same templates. This documents describes the flow and APIs that will eventually come into place. ## Template location There are two kind of templates: 1. system wide templates 2. user defined templates Both should be simple template files and preview for them should be obtained using the preview API. The richdocuments works as a preview provider so it should provide proper previews to use. ### System wide templates An admin can configure system wide templates. This can be done from the admin settings. These templates are stored in the AppData. > Note: it might require some less pretty code to get the previews out of the appdata. But since it will also work on 13 we have no real alternative. There are a few special templates that are shipped with the app. The empty files. They should always be available. ### User defined templates In the Collabora user settings the user can select a folder from where to load templates. This can be any folder the user has access to. So users can share template folders among each other. ### Replacing empty templates Empty template files can be replaced the existing files in `appdata_[instanceid]/richdocuments/empty_templates/`. The files can be reverted to the templates shipped with the release by running the `occ richdocuments:update-empty-templates` command.