Restoring or Publishing Previous Script Versions

Restoring a Previous Version

If after republishing your production script the changes are an issue on your website, you have the ability to restore to a previous version of the production script within the Cookie Consent application.

To restore or download a previous version of a script

Note:

Download functionality is only available to users leveraging Download to Local. If you require this functionality, contact OneTrust Support.

For more information, see Downloading and Deploying Scripts from Local Hosting.

  1. On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.

  2. Select the domain you want to restore to a previously published version.
  3. Navigate to the History tab.
  4. Hover over the row of a production script until the Context Menu icon appears.
  5. Click the Context Menu icon. The Context menu appears.

  6. Select Restore Download. A confirmation modal appears.


  7. Configure the Require users to re-consent setting. If you enable the setting, consent will be cleared for your website users. Every user will be prompted to re-consent after 24 hours.


  8. Click the Confirm button. Your script is reverted to the selected version.

    If you choose to Download, the previously published script will be downloaded just like if you use Download to Local in the Publish pane.

Note:

You will not need to alter the script on your website if you have only changed template, geolocation, or cookie categorization configuration.

If your most recent publish only involved enabling Auto-Blocking or changed the Enable Language Detection on Scripts to Determine the language from HTML page, you will not need to restore your script. All you will need to do is remove the added Auto-Blocking Script or data document attribute.

Choosing a Script Version to Publish

The Choose a script version to publish feature allows to you to publish configuration to a previous OneTrust version.

When publishing a script to an older version than the current OneTrust version (e.g., if OneTrust is on 202503.2.0, but you want to publish your script to the 202503.1.0 version), you will not be able to utilize any of the new features or bug fixes that were released with the most recent version of OneTrust (any features released with 202503.2.0).

If selecting an older version, there will be a list of features that are incompatible for the selected publish version. These features will still be able to be configured in the Cookie Consent application, but the script will not be able to use those features if publishing to an older version.

If you’re updating to a newer version of the script than your current published version, you’re going to be getting all the latest and greatest features and bug fixes. Additionally, with these new features and bug fixes, there may be some changes that could affect the custom CSS or custom JavaScript on your site. Thus, we recommend going to the test script and publishing the test script to the newer version and testing those changes before publishing to production. Additionally in the publish panel, there is a link to the release notes for you to be able to review changes before publishing.

Support to publish to a particular script version will last a minimum of four releases after that release. For example, when OneTrust releases 202503.2.0, this means that you will be able to publish to the 202503.2.0 version of the script until and including OneTrust releases the 202506.1.0 version (at a minimum).

If you have any concerns about publishing with a new script version, utilize the Testing CDN to test prior to publishing to production.

To publish a test script as a previous version

  1. On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.

  2. Select the domain for which you would like to re-publish the script.
  3. Click the Publish Test button.
  4. Select the version of the Script you want to publish.
    Note:

    The features incompatible with the new script version will be displayed.



  5. Click the Confirm button.
  6. Select your publishing options. For more information, see Publishing and Implementing Cookie Consent Scripts.

To publish a production script as a previous version

  1. On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.

  2. Select the domain for which you would like to re-publish the script.
  3. Click the Publish Production button.
  4. Select the version of the Script you want to publish.
    Note:

    The features incompatible with the new script version will be displayed.



  5. Click the Confirm button.
  6. Select your publishing options. For more information, see Publishing and Implementing Cookie Consent Scripts.

Using the Change Log

If applicable, the Publish panes contain any critical changes made since last publishing the script. Critical changes include but are not limited to:

  • Changing the consent framework.

  • Change the geolocations associated with a geolocation rule.

  • Changing the consent model for a geolocation.

  • Altering cookie groups.

The change log will not display cosmetic changes, such a branding or logos.

To view the change log

  1. On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.

  2. Select the domain for which you would like to re-publish the script.
  3. Click the Publish Production or Publish Test button.
  4. Navigate to the Critical Changes tab on the Publish Pane. The old and new values for the critical settings are displayed.


To view publication history

  1. On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.

  2. Select the domain for which you want to review the script's publication history.
  3. Go to the History tab.
  4. Review the publication history.