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. This way, you can easily discard changes. To create a copy of a plugin set, select the plugin set you want to edit from the Copy plugin set drop-down list when creating a new plugin set. |
Creating new plugin sets:
Go to Plugins » Plugin overview.
Click on Add ().
→ The New plugin set window opens.
Enter a name for the plugin set.
Save () the settings.
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.
If there is an update for a plugin, under Action, the Update button of the plugin is highlighted.
Updating marketplace plugins:
To update a plugin, click on the Update button.
→ A new window opens, allowing you select the version you want to install.
Select the version you want to install from the Version to install dropdown menu. The newest version is selected by default.
Note: A text field below the drop-down list shows the changelog of the currently selected version.
To update the plugin to the selected version, click on the Install button.
→ The plugin is updated.
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 commit.
If your Git repository contains a newer state of the plugin and you want to use it in plentymarkets, you can pull the branch.
To pull a Git plugin, open the Plugins » Plugin overview menu and click in the Action columns on Pull branch ().
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:
Go to Plugins » Plugin overview.
Click on the plugin set you want to edit.
→ The area for editing the selected plugin set opens.
Click on the Git plugin you want to edit.
→ The plugin detail view for the selected plugin opens.
Go to Git.
Click on Pull ().
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.
Switching branches:
Go to Plugins » Plugin overview.
Click on the plugin set you want to edit.
→ The area for editing the selected plugin set opens.
Click on the Git plugin you want to edit.
→ The plugin detail view for the selected plugin opens.
Go to Git.
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.
If you want to use a different state of your repository, but didn’t create a branch for it, you can also access individual commits.
Switching commits:
Go to Plugins » Plugin overview.
Click on the plugin set you want to edit.
→ The area for editing the selected plugin set opens.
Click on the Git plugin you want to edit.
→ The plugin detail view for the selected plugin opens.
Go to Git.
Copy the commit ID of the commit you want to switch to.
The last 50 commits of the selected branch are displayed in the detail view. You can copy a commit ID by clicking on Copy commit ID to clipboard. () in the row of the commit. If you want to switch to an older commit, you can perform the same steps in the commit overview of your Git repository.
Paste the copied ID into the Commit ID field.
Click on Checkout.
→ Or: If you want to switch to one of the last 50 commits, you can also click on the name of the commit and confirm the switch by clicking on Ok.
→ A message confirms that you have successfully switched to the provided commit and Head@Commit_ID is displayed as branch. These settings are saved automatically.