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

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