Using Versioning in TOWeb

The versioning feature introduced in version 13 of TOWeb under Files > Versioning (CTRL + G) allows you to create and manage multiple versions of your website within a single project without having to merge modifications. Unlike using backup/restore or creating separate sites, versioning offers several significant advantages:

• Centralized Management: All versions of your website are contained within a single project, making it easier to manage and organize your modifications and evolutions. There's no need to juggle between multiple backup files or separate projects.
• Time Saving: Creating versions is quick and simple. You can instantly create a new version, make modifications, and switch between versions without having to restore backups or duplicate an entire site.
• Easier Comparison: You can easily compare the different versions of your site, preview changes, and even revert to a previous version with a single click, without affecting the live version.
• Reduced Risk of Errors: By using a single site with multiple versions, you reduce the risk of losing modifications or confusing different versions during restorations or site duplications.

The versioning feature is managed under Files > Versioning (CTRL + G) in TOWeb.

1. Enable Versioning on the Site

Enabling versioning on your site allows you to manage multiple versions of your website directly in TOWeb. When you enable this feature, TOWeb automatically creates an initial version named "version-1", which corresponds to the current state of your site. This version becomes the starting point for managing your different versions. It is recommended to immediately rename "version-1" to better identify its role, such as "production", for example.

All modifications made in TOWeb are applied and saved to the active version.

2. Add a Version

Adding a new version allows you to create a copy of the active version of the site to make modifications or improvements. Before adding a new version, make sure to activate the version that will serve as the starting point. The new version created will be an exact copy of the active version at the time of creation, allowing you to test or prepare modifications without affecting the live site.

3. Activate a Version

Activating a version means replacing the current site content with that of the selected version. This action switches the entire site to the state of the chosen version, making it visible and active for site visitors. Use this action with caution, especially in production, to avoid displaying unfinished or untested modifications.
You cannot change the active version while there are ongoing modifications: you must either save them or cancel them with the "Undo" (  ) function introduced in TOWeb 12.

4. Rename a Version

Renaming a version allows you to modify the name of the selected version without any impact on the site content or state. The active version remains unchanged, only the version label is modified. This helps you better identify the different versions of your site, such as "production", "development", or "archive". This action is particularly useful for organizing and clarifying the management of your versions.

5. Delete a Version

Deleting a version permanently removes the selected version from TOWeb. This action is not reversible, so be sure you want to delete the version. It is impossible to delete the currently active version. If you wish to delete the active version, you must first activate another version and then delete the old version. This action is useful for freeing up space when the number of versions is limited by your license.

6. Disable Versioning on the Site

Disabling versioning deletes all existing versions of the site except the active version. The currently active version will be preserved, but all other versions will be permanently lost. Before disabling versioning, make sure that the version you want to keep is active, as there will be no way to recover the other versions after this operation. This action should be used with caution, especially if you want to revert to simpler site management without versioning.

Here are some examples of how to take full advantage of this feature:

1. Create Versions for Seasonal Events or Promotions

You can create a new version of your site dedicated to specific events, such as Christmas, sales, or temporary promotions. This allows you to prepare appropriate content while keeping the main version intact.

Example:

• Main version: "site-official"
• Event version: "site-christmas" with graphics and content specific to the holiday season.

2. Prepare the Next Major Version of Your Site

Work on a new version of your site (redesign, adding new features) without affecting the live version. This way, you can test and preview changes before they go live.

Example:

• Current version: "site-v1" (live)
• New version: "site-v2" (with new design, new sections, etc.)

3. Create Versions for Tests or Experiments

Create versions of your site to test specific modifications, such as adding new sections or changing the theme. This allows you to experiment without risking your main version.

Example:

• Main version: "site-official"
• Test version: "site-test-theme" to try out a new theme.

4. Manage Versions for Different Languages

Create a distinct version of your site for each language, simplifying translation management and ensuring each version is independent.

Example:

• French version: "site-fr"
• English version: "site-en"
• Spanish version: "site-es"

5. Create a "Restore Point" Before Major Changes

Before making major changes to your site, create a backup version. This way, you can easily revert to the previous version if needed.

Example:

• Main version: "site-official"
• Backup version: "site-official-backup"

6. Manage Multiple Projects or Clients

For users who manage multiple websites or projects from a single site model, each version can represent a separate project, allowing you to keep all your work organized.

Example:

• Client A version: "site-client-A"
• Client B version: "site-client-B"

7. Archive Old Versions of Your Site

Create archived versions of your site at different times to keep a history. This way, you can view or restore an old version if necessary.

Example:

• "site-2023-Q1": archived version of the first quarter of 2023
• "site-2023-Q2": archived version of the second quarter of 2023

8. Experiment with New Ideas or Concepts

Create separate versions to test new ideas, such as a new layout or adding an online store. Easily compare these experimental versions with your main version.

Example:

• Main version: "site-official"
• Experimental version: "site-experiment-1" (testing new concepts)

9. Create Region-Specific Versions

Create versions of your site tailored to different regions, with content customized for the target audience.

Example:

• Europe version: "site-europe"
• USA version: "site-usa"

10. Create Tutorials or Demonstrations

Create versions dedicated to demonstrations or tutorials without affecting the main version of your site.

Example:

• Tutorial version: "site-demo"
• Main version: "site-official"

You want to manage two versions of your site: a live production version and a development version for preparing future updates. If you have a TOWeb license that does not offer unlimited versions (STUDIO version), we will illustrate this example by rotating between only 2 versions to work efficiently on your site.

• When you enable versioning for the first time, TOWeb automatically creates an initial version called "version-1". This is the current version of your site, which becomes the production version.

• Select "version-1" and rename it to "production" to clearly identify that it is the live version.

• Add a new version to start working on the future modifications of your site. Name this new version "development" or "future-version".

• Activate the "development" version to make the necessary modifications. All changes you make will be saved in this version, while the "production" version remains unchanged and visible to your site visitors.

• Once the modifications are complete and ready to go live, you need to replace the current "production" version with the "development" version.

• First, activate the "production" version. This prepares it to be modified or replaced.

• Delete the current "production" version to free up space, as your license only allows two versions. Warning: Make sure that all necessary changes are ready in the "development" version before deleting the current production version.

• Rename the "development" version to "production" to indicate that it is now the official live version.

• Add a new version based on the new "production" version you just created. Name it, for example, "new-updates" to prepare for future changes. You now return to the initial configuration, with a "production" version and a "development" version.

With this workflow, you can always maintain your site in production while preparing future updates. You can repeat these steps whenever you want to update your site without disrupting the version visible to your visitors.

If you have a STUDIO license with unlimited versions, you can adapt this example to keep/archive as many versions as you need.

Free TOWeb License

Versioning is not available in the free version of TOWeb.

PREMIUM and e-COMMERCE Licenses

• You can create a maximum of 3 versions per site/project. This allows you to handle most of the scenarios mentioned above, and notably to work by rotating between a production version and a future version of your site, for example named "production" and "future".
• Site backups and restores systematically include versioning information for your sites.

STUDIO License

• The number of versions is unlimited.
• Two additional options are available for backup/restore for sites with versioning enabled:

1. Backup Only the Active Version: When creating a backup (WGA file) of a site with versioning enabled, a checkbox allows you to choose to back up only the active version of the site. This option generates a standard WGA that excludes versioning-related files and folders. This is a very partial backup (only one version) that should only be used in specific cases, for example if you are creating sites for third parties and want to send them a backup of their site without including versioning information.

2. Restore a Site in the Active Version Only: When restoring a WGA file, a checkbox allows you to restore its content only in the active version of the site, without overwriting or deleting other existing versions. This option excludes any versioning files and folders present in the restored WGA file, to preserve the existing versions in the target site and limit the restoration to the active version only. With this option, you can aggregate previously separate sites into a single project. For example, if you had three variants A, B, and C of the same site managed separately, enable versioning on site A, rename "version-1" to "site-A", and create versions "site-B" and "site-C", then restore the WGAs of sites B and C. You now have a single project with three versions/variants of your site, which is much more convenient.