• 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.

WordPress Installations Scan finds 4 unidentified WP installations

Peter Downes

Basic Pleskian
Hello Community

The Plesk WordPress Installations Scan returns x4 installations with no details (ie. a name of '/httpdocs' but no URL, themes, plugin details etc.)

The does return x15 other installations correctly.

I can account for two of the installations as they are missing from the list of 15. Perhaps each is being duplicated?

Has anybody else fixed this problem?
Thanks
 
Hi Peter,

This generally indicates that WP installations are either very outdated (3.3 or earlier), or somehow broken. Is there anything specific about these installations?
 
Hi,
I encountered the same problem and I confirm that it concerns broken installation or outdated version of WP.
My only concern is that from the WordPress Toolkit end-user interface, there's no indication of the full path where the installation has been detected for such case. Therefore, it's required to search manually across the server to find out which installation is concerned. Would that be something interesting to add such information as the full path in a new version of the WP Toolkit?
 
Last edited:
Thanks for the feedback guys.

I'm sure you are right. Broken installations or outdated version of WP would explain the issue - in some cases.

But I've checked this morning and a website that is 100% updated and appears to be functioning normally is not listed.
It was listed two days ago.

Perhaps it is to do with the security plugin or permissions on wp-config or the directory.
I'll keep an eye on it.
 
Back
Top