How to keep custom theme settings when upgrading Tiki — best practices & pitfalls?
Hi everyone,
I’m running a site built with Tiki, with a custom theme and several theme-overrides (CSS tweaks, custom template files, some plugin integrations). As Tiki evolves, I expect to update it regularly — but I also worry about losing customisations or running into compatibility issues after upgrades.
I’d like to ask the community:
What workflow or practices do you recommend to preserve custom theme settings and overrides across upgrades of Tiki?
Are there version control / backup strategies that work well (e.g. using Git, storing diff patches, or a separate child-theme approach)?
Have you encountered common pitfalls — e.g. upgrade breaking template structure, CSS class renames, deprecated hooks — when upgrading from one Tiki version to another?
How do you test custom themes safely before applying an upgrade to the [SPAM LINK REMOVED] production site?
I’d love to hear your real-world experiences, scripts or procedures you use, or any resources/documentation that help manage this safely.
Thanks in advance for your feedback!