• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Wordpress Toolkit not updating all Themes/Plugins

Does this happen to anyone else?

  • Often

    Votes: 2 66.7%
  • Sometimes

    Votes: 0 0.0%
  • Never

    Votes: 1 33.3%

  • Total voters
    3

Craig

New Pleskian
How can I 'force' Wordpress Toolkit to rescan themes and plugins?

A handful of themes and plugins are often present with different version numbers. WP Toolkit will recommend upgrades but only some of the installations are upgraded when ticking the box and selecting upgrade leaving orphaned themes or plugins that require logging into the specific WP install to upgrade.themes.jpg plugins.jpg
 
Hi Craig,

consider to DETACH your wordpress installations if you experience described issues and pls. make sure, that your Plesk Wordpress Toolkit is up-to-date ( current actual version is "Version: 2.0.2-315" ). ( => HOME > Wordpress > (choose the name of the wordpress instance ) Detach )

Afterwards, SCAN again for (new/old) wordpress instances, so that the WP Toolkit attaches the previous detached wordpress instances again. ( => HOME > Wordpress > Scan )
Selecting the depending wordpress instance and choosing the option "Update", should force the update of the choosen wordpress instance(s). ;)
 
Hi Craig,

consider to DETACH your wordpress installations if you experience described issues and pls. make sure, that your Plesk Wordpress Toolkit is up-to-date ( current actual version is "Version: 2.0.2-315" ). ( => HOME > Wordpress > (choose the name of the wordpress instance ) Detach )

Afterwards, SCAN again for (new/old) wordpress instances, so that the WP Toolkit attaches the previous detached wordpress instances again. ( => HOME > Wordpress > Scan )
Selecting the depending wordpress instance and choosing the option "Update", should force the update of the choosen wordpress instance(s). ;)

Wouldn't making an option which allows to "reattach" a specific WP site make sense? Doing the detach and directly re-atach including restoring configured settings and options from WP toolkit.
This happened several times on our setups as well. Having to deatach and configure all over again takes time.
 
Wouldn't making an option which allows to "reattach" a specific WP site make sense?
Yes, it does make the update tool somewhat unusable when it doesn't detect updates. I'd like to use this as it saves time, but I'm more inclined to update the plugins manually from within the CMS. Please fix this.
 
Yes, it does make the update tool somewhat unusable when it doesn't detect updates. I'd like to use this as it saves time, but I'm more inclined to update the plugins manually from within the CMS. Please fix this.

+1, same issue
Do you have CloudLinux as OS?
 
Back
Top