Skip to content
Logotype Sitevision Developer
Log in
Log in

Addons version limit

In order to improve performance, optimize storage, and streamline the user experience, Sitevision 2025.03.1 introduces a version limit for addons. Previously, addons could accumulate an unlimited number of versions, leading to unnecessary resource consumption and a cluttered interface. With this update, the number of stored versions is now capped, ensuring a more efficient and manageable system.

Published: 2025-03-10

In Sitevision 2025.03.1 we’re reducing the number of versions an addon can have to 5. Previously, this number was in theory infinite - leading to unnecessary use of storage, memory allocation and a cluttered UI. Exceeding this limit will now automatically remove the oldest non-active version - same as to how Sitevision Marketplace’s auto update works.

The default version limit for new addons is 3, if left unspecified. This will also be the limit for existing addons with 3 or less versions. There is also the possibility of changing the version limit for a specific addon under its settings, to somewhere between 2 and 5.

Version limit property in the Addon settings

When lowering the version limit, versions will be removed upon uploading a new version - not as the setting itself is saved, so there is time to backpedal if a mistake has been made.

Uploading a new version via the edit interface will give you a heads up that the oldest non-active version will be removed if the version number exceeds the limit. Deploying a new version via the REST-API does however not output this warning.

Creation of an Addon via the REST-API now allows you to specify the version limit (i.e. if you don’t want the default value of 3). Example:

How does this affect me?

Practically, it shouldn’t. No matter how many new versions you deploy, the active version will never be removed. Just beware that if you deploy 4 untested versions, a stable non-active version that you were going to set as active will be gone. This is however rarely the case as during development you would typically use force-deploy which updates a single version in such cases.