Change the client area templates
An update replaces the files ClientFence ships. Make your changes in the places below, and an update keeps them.
| What to change | Where | Kept on update |
|---|---|---|
| Colours, links, dashboard and footer | Palisade settings | Yes |
| Your own CSS | Custom CSS in the Palisade settings | Yes |
| Logo and company details | Company and branding | Yes |
| A client area page or part of one | themes/palisade/html_custom/ |
Yes |
| Email text | Email templates | Yes |
| New pages | Custom pages or a module | Yes |
| Extra content on an existing page, a menu link | A module widget | Yes |
| The whole look, many pages | A theme of your own | Yes |
Files in themes/palisade/html/ |
No: the update writes over them |
Change a client area template
Section titled “Change a client area template”ClientFence looks for each client area template in themes/palisade/html_custom/ first, then in
themes/palisade/html/, then in the modules. A file in html_custom with the same name wins.
- Create the folder
themes/palisade/html_custom/in the ClientFence directory. - Copy the template you want to change from
themes/palisade/html/into it, keeping its name and any subfolder (for examplepartials/footer.html.twig). - Edit the copy and make the web server user its owner.
- Reload the page. If the change does not show, go to System → Settings → System, open the Cache tab and select Invalidate cache.
The admin theme works differently: ClientFence ships its own files in
themes/admin_default/html_custom/, and an update replaces them.
Twig and scripts
Section titled “Twig and scripts”Templates use Twig. Scripts need the page’s nonce: <script nonce="{{ csp_nonce }}">. Inline
onclick attributes do not run. Twig filters, functions and variables
lists everything a template can use, and the JavaScript API the
scripts can call.

