Updating installed plugins

Occasionally, plugin developers may provide a new version of their plugin. If you’ve already installed such a plugin in a plugin set, you have to update it to use the new version. Since this means changing your plugin set, you should create a copy of your plugin set before updating the plugin.

Backup

If you want to edit your plugin set, create a backup copy first. Using a backup copy has the following advantages:

  • If the changes cause any problems, your online shop isn’t affected. This means you can first check your pages in a preview and publish them afterwards.

  • It’s easy to discard changes.

To create a copy of a plugin set, open the Plugins » Plugin set overview menu. Then, click in the Actions column on the Copy plugin set button ().

Creating new plugin sets:

  1. Go to Plugins » Plugin set overview.

  2. Click on Create new plugin set ().
    → The New plugin set window opens.

  3. Enter a name for the plugin set.

  4. Click Create.
    → The plugin set is created and appears in the list of plugin sets.

Depending on whether you purchased the plugin from plentyMarketplace or added it to your system via Git, the possibilities you have for updating are different.

1. Marketplace plugins

If there is an update for a plugin, under Action, the Update button of the plugin is highlighted.

Updating marketplace plugins:

  1. To update a plugin, click on the Update available button ().
    → The Update menu opens.

  2. Select the version you want to install from the Select version drop-down list. The newest version is selected by default.

  3. To update the plugin, click on Update.
    → The plugin is installed in the new version.
    → After installation has finished, the plugin set opens.

  4. Save () the plugin set.
    → If there’s a problem with saving the plugin set, click on View details to receive further information.

Marketplace plugins cannot be downgraded to an older version. If you want to use an older version of the plugin, you have to delete and then reinstall it.

2. Git plugins

You can update a Git plugin in different ways. To use a newer version of the current branch, you can pull the branch. But, you can also use a different branch by changing branches or use an older version of the plugin by checking out any tag.

2.1. Pulling branches

If your Git repository contains a newer state of the plugin and you want to use it in PlentyONE. you can pull the branch.

Removed in Plugin Build 2

Starting on 25 July, 2022, a new deployment process (Plugin Build 2) will be gradually released on all PlentyONE Systems. The new deployment process automatically updates Git plugins that you’ve installed via a branch to the newest version.

When your system has been switched to Plugin Build 2, the UI will no longer include actions for pulling branches.

To pull a Git plugin, open the Plugins » Plugin set overview menu. Open the plugin set you want to edit by clicking on the table row. Then, click in the Actions column on the Pull button ().

Alternatively, you can pull Git plugins in the Git detail view. Here, you can also view the latest 50 commits of the selected branch.

Pulling Git plugins

Pulling Git plugins:

  1. Go to Plugins » Plugin set overview.

  2. Open the plugin set you want to edit by clicking on the table row.
    → The plugin set opens.

  3. Open the settings of the Git plugin you want to edit by clicking on the table row.
    → The plugin detail view for the selected plugin opens.

  4. Click on Git.

  5. Click on Pull ().

2.2. Switching branches

You can switch between branches of a Git repository. Branches are local settings. In other words, you can use the same plugin in multiple sets, but work with different branches. This is useful if you want to, for example, use a stable branch in your active plugin set and test a new feature in an inactive plugin set at the same time.

Automatic pull in Plugin Build 2

Starting on 25 July, 2022, a new deployment process (Plugin Build 2) will be gradually released on all PlentyONE Systems. The new deployment process automatically updates Git plugins that you’ve installed via a branch to the newest version.

When your system has been switched to Plugin Build 2, you’ll be informed about the changes when you deploy a plugin set that contains Git plugins for the first time. If you want to prevent the deployment process from updating a Git plugin automatically, switch to a tag.

Switching branches:

  1. Go to Plugins » Plugin set overview.

  2. Open the plugin set you want to edit by clicking on the table row.
    → The plugin set opens.

  3. Open the settings of the Git plugin you want to edit by clicking on the table row.
    → The plugin detail view for the selected plugin opens.

  4. Click on Git.

  5. From the Branch drop-down list, select the branch you want to switch to.
    → A message confirms that you have successfully switched to the selected branch. These settings are saved automatically.

2.3. Switching tags

If you want to use a different state of your repository, but didn’t create a branch for it, you can also access individual tags.

Switching tags

  1. Go to Plugins » Plugin set overview.

  2. Open the plugin set you want to edit in the side navigation.
    → The plugin set opens.

  3. Open the settings () of the Git plugin you want to edit.
    The plugin description opens.

  4. Click on Git.

  5. Choose under Tags the version tag you want to switch to.
    → The window Change branch opens.

  6. Click on Switch.
    → A message confirms that you have successfully switched to the selected tag.

  7. Afterwards open the plugin set again and deploy it (cloud).
    → After the deployment the changes are adopted.