Resolved Wordpress Toolkit "scan" feature is now broken...

[AndreasY]

One of the recent updates had broken the "scan" feature found in the WordPress Toolkit.

When I say broken, what I mean is that the "scan" feature no longer detects WordPress installations ....

Hope this is fixed soon and not a few years later down the line ....

 

[Aleksey Filatev]

Thank you for reporting this. Could you please share some details to make it easier to investigate:

• Do you previously detached this website from the toolkit?
• Is this website installed into the domain root (httpdocs) or subfolder?
• Is your website has a standard file structure (wp-content and wp-includes in the website root and wp-config.php in the same directory or one level above) or it has some customizations?

Your answers will help us to provide the fix or a workaround as quick as possible.

 

[AndreasY]

Hi,

thank you for your reply, I did not expect to get one !

Do you previously detached this website from the toolkit?

I have done this for a new domain, i.e. manually add wordpress directory with files/folders and manually attach database and I have tested also on a domain that already had a Wordpress install setup via the toolkit by removing the WordPress entity (not delete) and pressing scan again.

Is this website installed into the domain root (httpdocs) or subfolder?

Both domains are installed in sub-directories

Is your website has a standard file structure (wp-content and wp-includes in the website root and wp-config.php in the same directory or one level above) or it has some customizations?

Yes, both are standard file structure

Look below comments in this article

https://support.plesk.com/hc/en-us/articles/360008289873-How-to-add-a-domain-with-installed-WordPress-in-WordPress-Toolkit-in-Plesk-

Huib van Wees
On February 24, 2022 14:37

Found the same issue.

Thanks

 

[Aleksey Filatev]

Thank you for answers! Could you please check that there is no hidden file .wp-toolkit-ignore in the root of website?

 

[AndreasY]

Thank you for answers! Could you please check that there is no hidden file .wp-toolkit-ignore in the root of website?

For the domain that was created with the toolkit and then removed this file exists.

For the domain that was manually created it does not exist.

 

[AndreasY]

I removed the .wp-toolkit-ignore file after having read its contents and it made no difference.

 

[Maarten]

Same here. When you detach a WP site from the WP Toolkit and remove the .wp-toolkit-ignore, a new scan will not get it back into WP Toolkit.

CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.42 Update #1
WordPress Toolkit Version 5.10.0-6098

 

[Kaspar]

When you detach a WP site from the WP Toolkit and remove the .wp-toolkit-ignore, a new scan will not get it back into WP Toolkit.

Did you use the file manager by any change to delete the .wp-toolkit-ignore file? If so, is the file perhaps still in the file manager trash can?

 

[Maarten]

Did you use the file manager by any change to delete the .wp-toolkit-ignore file? If so, is the file perhaps still in the file manager trash can?

Nope, I'll deleted it on the commandline. It's gone.

 

[Maarten]

I've created a report for this:

Forwarded to devs - WordPress Toolkit: 'scan' doesn't work anymore

Username: TITLE WordPress Toolkit: 'scan' doesn't work anymore PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 7.9.2009 (Core) Product Plesk Obsidian Version 18.0.42 Update #1 WordPress Toolkit Version 5.10.0-6098 PROBLEM DESCRIPTION When you scan for a new WordPress...

talk.plesk.com

 

[custer]

Hey everyone,

Thank you for reporting this issue and providing a lot of useful info. We have found the root cause and we're planning to publish an update that fixes this issue ASAP.

 

[custer]

Update: WPT v5.10.1 with the corresponding bugfix is now out. Thanks to everyone who helped report and identify the issue, and sorry for the inconvenience!

 

[Maarten]

Thnx!

It works again for non-administrator users, but not when you're the admin of the server.
Has this always been the case or is this a change in the scan procedure?
How can I attach an existing WP site as an administrator?

 

[AndreasY]

Update: WPT v5.10.1 with the corresponding bugfix is now out. Thanks to everyone who helped report and identify the issue, and sorry for the inconvenience!

Thank you, its working now for both the domains I tested on.

However, I have not understood how this fix got applied seeing that no updates were detected by Plesk to install and I did not install anything manually.

Does somebody here know the procedure that applies such a fix with no notifications from either an automatic update or a manual update being available ?

 

[AndreasY]

So I can see the following

Version 18.0.42 Update #1, last updated on Mar 18, 2022 10:06 AM

From the release notes its clear that the fix is March 22.

So how this update get pushed across and is there other stuff that gets pushed across without appearing to the end user ???

 

[Maarten]

If you go to Extensions and select the "Updates" tab, there is an option to enable/disable auto-update.
There is no message given when an update is installed.

 

[AndreasY]

If you go to Extensions and select the "Updates" tab, there is an option to enable/disable auto-update.
There is no message given when an update is installed.

Hi!

Thanks for the info,

OK, ive understood my misunderstanding.

The "WP Toolkit" is an extension, I was thinking its a core component of Plesk, hence the reason nothing appeared in the notifications area when it was updated.

So ive now understood that when an extension is updated we do not receive any notification.

 

[Maarten]

I get it ;-)

Best thing to do is to keep a eye on the change log:

Change Log for Plesk Obsidian

Find out about changes, additions and updates to Plesk Obsidian on an iteration to iteration basis.

docs.plesk.com

Not only does it contain changes but also tips on how to activate or disable new features etc.

 

[Aleksey Filatev]

> How can I attach an existing WP site as an administrator?

@maartenv Is this question still actual? By design, the scanning should works the same way for administrator, customers or reseller. The difference is the area of scanning. For customer its limited by his own subscription(s), but for administrator it is the server wide scanning.

 

[Maarten]

Hi,

I've just tested it again on 2 servers:

- scanning on server 1 seems to be working as an admin.

- scanning on server 2 still can't find the detached WP installation:
Firefox console log:
XHR POST https://server2:8443/modules/wp-toolkit/index.php/domain/scan [HTTP/1.1 200 OK 532ms]
XHR OPTIONS https://firehose.us-west-2.amazonaws.com/ [HTTP/1.1 200 OK 746ms]
XHR POST https://firehose.us-west-2.amazonaws.com/ [HTTP/1.1 200 OK 182ms]
XHR POST https://server2:8443/modules/wp-toolkit/index.php/domain/get-background-tasks-data [HTTP/1.1 200 OK 467ms]
XHR GET https://server2:8443/modules/wp-toolkit/index.php/domain/get-initial-data [HTTP/1.1 200 OK 577ms]
XHR POST https://server2:8443/modules/wp-toolkit/index.php/domain/get-instances-data/withAssets/1 [HTTP/1.1 200 OK 2304ms]

Server 1 =
CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.42 Update #1
WordPress Toolkit Version 5.10.1-6111

Server 2 =
CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.42 Update #1
WordPress Toolkit Version 5.10.1-6111