Player Versioning
Choose whether you want your embed to use the latest version of the Zentrick Player or lock it to a specific version.

Rationale

While you’re creating your experience in the Zentrick Studio, you’re implicitly using the latest and greatest version of the Zentrick Player. That’s all well and good, but what happens after you’ve published it?

By default, we always give you the latest version that’s (to our best knowledge) compatible with your published experience. To achieve this, we use a concept called Semantic Versioning. In a nutshell, that means that the Player’s version consists of three levels: major, minor, and patch. For example, if you’re on Player version 2.1.24, that means major version 2, minor version 1, and patch version 24.

When the major version changes, there is no guarantee that anything will keep working. Thus, we only increment the major version of the Player when we introduce changes that may break existing experiences. You’ll find that we have been on major version 2 for quite a while, so every Player version out there should actually be backward compatible.

Minor version bumps mean that we’ve added one or more new features. Contrary to major version bumps, minor ones shouldn’t break anything. Nevertheless, since your experience (probably) doesn’t use any of the new features, you might not want to risk including them either.

Finally, patches are used to fix issues within a minor version. Consequently, you would only refer to a specific patch version if you wanted to be absolutely sure that everything stayed as it was at the time of publication. In all other instances, we recommend that you at least use the highest patch version to make sure that you get all the latest bugfixes.

Selecting a Version

At the time of this writing, there is no graphical interface that lets you specify the player version to use. However, in many instances, you can easily switch to a different version number.

Finding Your Version

To select a Player version, you’ll first need to find out which version your experience was published against. The easiest way to do so is by viewing the source code of your watch page; i.e., watch.zentrick.com followed by the publication ID.

In the watch page’s source, you’ll find a <script> tag referring to a file called loader.js. The URL of that file will contain the major and minor version number. For example, /v/2/1/loader.js means that your major version is 2 and your minor version is 1. That will automatically give you the latest patch within that minor version.

Changing Your Version

On our watch pages, we don’t let you change the version number at this time. We prefer to keep those nice and simple.

In most other distribution scenarios, you can use whichever version you like. As mentioned, we recommend against switching major versions as this is highly likely to cause compatibility issues. You may, on the other hand, want to explicitly specify a patch version. Conversely, you can specify only a major version to make sure that you’re always using the very latest version that’s still compatible.

To select a version, alter the URL to the file on Zentrick’s servers to include the version you’d like to use. For example, https://watch.zentrick.com/v/2/1/player.js would give you the latest patch to version 2.1 of the Player JavaScript API. If you wanted to use version 2.1.5 explicitly, you would change the path to /v/2/1/5/player.js. To use the latest patch within major version 2, the path would be /v/2/player.js.

Legacy Embed Code

If you published your experience before we introduced Semantic Versioning, you’re probably using URLs along the lines of https://watch.zentrick.com/-/player.js. At the time of this writing, we mirror the latest version of the Player at that location. We recommend that you switch to the new URL format as support for the legacy URLs will most likely be dropped in the foreseeable future.

Oops! Your screen is too small for this website.