A published theme keeps working as Tringify adds features. Build against what these docs describe, and your theme renders the same way for as long as a store uses it.
What stays the same#
Area |
What you can rely on |
|---|---|
Vascula |
Tringify updates the Vascula version it uses only once published themes render the same with it. |
Platform filters |
Existing filters keep their arguments and output. New filters may be added. |
Store data |
Names and types stay as they are. New fields and new |
Schema |
Setting types, schema fields and form kinds are only ever added. Nothing you declared becomes invalid. |
Review |
New checks apply to new versions. A published version is never failed by a check added later. |
How new features arrive#
New features appear as new data, settings or filters. A theme that does not use them is unaffected, and you can adopt them in your next version.
Keep your theme compatible#
- Use only behavior these docs describe.
- Check for optional data with
{% if %}before you use it. - Test a real update as well as a fresh install; see Packaging & Sealing.
If a published theme renders differently after a platform update, with the same section and the same data, report it to developers@tringify.com.