Use a Theme Version - Enhanced System
Once a version has been added to Theme Repository, you can add it on many platforms. This is the documentation that explains how to use it.
This is for platforms where you only need to get a version from another theme without doing any code changes on this theme on this platform. For example:
on production or preprod
I am working on my extension, and I want to have the latest version of a theme maintained by another team
If your goal is to edit the code and work on it on this platform, please do a git clone instead
If you are on a platform shared with other teams, do not change the version of a theme owned by another team without discussing with them 😄
Theme Version 2.0 System
Whenever a theme is using Theme Repository, every theme versions are now being added by default to the "Version" section.
🆕 This is why there is no ADD button available on the Version section anymore.
There is now 2 sections related to Version & History within a Theme:
"Version" section: this section is listing every version available within the current platform
"Activation History" section: this section allows to keep track of the changes history. On each version switch, the change is saved in a new "Version history" tab
Main benefits 🚀
It reduces manual work ⏩ all versions are now available by default, so users no longer need to add them manually.
It optimizes resource usage 🌿, helping to prevent size-related issues—especially for RWS teams that frequently switch between theme versions (e.g., Web Support).
How to change a theme version ?
1 / Open the theme "Version" section
Open the bento menu in the header, click on “Admin” icon
In the sidebar, open "System Management" section and click on “Themes”,
Then select your theme among the list available
If your theme is not present, you can add it with the ADD button and select it from the Theme Repository.
Go to the tab “Version”: the system displays by default every theme versions that has been pushed.
2/ Use the version
In the versions list, choose the version you want to use
On the detail page, you can select the Status “Current” and save
That's it: the new version setup as "current" corresponds to the current version of your theme on your platform!
Each platform can choose which tags are visible in the backoffice settings (editable only by admin).
For example, on production, only the versions tagged as "production" are visible, to prevent someone from selecting by mistake a "preprod" version
3/ "Activation history" section: check when a version has been changed and why
On each version switch, the change is saved in a new "Version history" tab
The list has the following columns:
Version Date: date & hour when the version was set as current
Name: Name of the version with the tag, for example:
tc-release-95 (production)
⚠️ If the version is no longer available on Theme Repo, you will see "Version deleted from Theme Repo" as the name
User: email of the user who set the version as current
Version ID: Theme Repo ID of the version that was activated
Notes: on the list view, we display a YES / NO status dependending whether the Activation History item has notes added in the "notes" field
Notes field can be useful to add any information to explain why this version was activated or reverted. This can be helpful in case someone had to revert to an old version and want to explain why.
Tag:
Corresponds to the tag configured when adding the version
⚠️ If the version is no longer available on Theme Repo, you will see an empty tag
Last updated