• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Unable to update plugin Asset with version has different owner in WordPress instance # /.wp-toolkit_

MarcoD

New Pleskian
Hello,
wordpress toolkit smart update plugin issue.

Is it a BUG? Is there a FIX or a Workaround?

Thank you, best regards


Updating the website:
- Unable to update plugin 'addon_***', details: Asset 'addon' with version '***' has different owner in WordPress instance #97 ('https://***.com/.wp-toolkit_9')

Selected items were updated with errors:
- Unable to update plugin '***', details: Unable to find an appropriate plugin version name = '***' sourceId = '2' version = '2.1.14' guid = '***'
 
Looks like the issue is related to the bug EXTWPTOOLK-4584: Unable to update the plugin/theme with an underscore in the name.
This bug will be fixed in one of the nearest extension updates. You may keep tracking of the Plesk Change Log to see when it will be fixed.

While the fix is not released, you can apply the workaround below (if possible):

1. Log in to the Plesk GUI
2. Go to WordPress > example.com > click Plugins (or Themes)
3. Disable the plugin (or theme) with an underscore in its name
4. Go back to WordPress > example.com > click Updates > and install the pending updates
 
Hello Igor,

thanks for the workaround.

It meant not using SMART UPDATE for these Plugins, which makes SMART UPDATE obsolete.
Almost a year later the issue persists with another error-message:

- Smart Update test run could not be performed due to errors. Address the errors and try running Smart Update again.
  • Unable to update plugin...
- Unable to find an appropriate plugin version name


The same PLUGINS still can't be updated through SMART UPDATE. Do you understand where the problem lies?

Best regards

Marco
 
Back
Top