Question Why Plesk controls my self-installed (FTP upload) Wordpress installation since last update

[jmar83]

Server operating system version

Debian 10.13

Plesk version and microupdate number

Plesk Obsidian 18.0.67 Update #2

Why Plesk controls my self-installed (FTP upload) Wordpress installation since last update? I don't understand why!?

I don't want that - so how to disable?



Thx for feedback(s)

 

[Raul A.]

Hi,
Simply detach the WordPress installs you don't want to manage via WordPress Toolkit.
Click on ...Mehr
Why don't you want the WordPress install to be manageable via WordPress Toolkit?

 

[jmar83]

Thx!

<Why don't you want the WordPress install to be manageable via WordPress Toolkit?>

I think it will result in compatibility problems when i don't update wordpress (due to some reason, custom thing they require older php version and so on... but yes, i know, will maybe result in security problems, but i also have OWASP webapp firewall with high security and IP blocks enabled in plesk... no problems with that since many years...)

 

[jmar83]

Hmmm... but why it shows 2 times the same website (entry 2 + 3) - but with different versions (and different security problems) when expand it on the left side with that arrow down icon.

Does it recreate a new "snapshot" on every WP update?


And: Do i need to press "Disconnect" ("Trennen") or Remove ("Entfernen") - i think "Disconnect" and not "Remove" (otherwise it will delete the whole FTP upload on domain?)

 

[Raul A.]

You get 2 instances because you have the entire WordPress or just parts of it in the document root and in some other folder (in the document root or in the webspace). WordPress Toolkit will scan all the folders for wp-config.php (this is my assumption) and will show in the interface all the installs that were detected.

Detach/Disconnect will remove the instance from WordPress Toolkit leaving the files in place.
Remove will remove the instance from WordPress Toolkit but will also remove the files and database!!!

I would recommend detaching the invalid instance then removing it manually (you might remove the live database if you simply remove it, in case both instances use the same database)

Once detached, a .file (can't remember the actual name) is created in the document root preventing future discovery of that install

The update settings can be controlled from WordPress Toolkit. You enable or disable auto updates.

If you get WordPress Toolkit Deluxe, you can effortlessly test updates and PHP version changes.

If you get WordPress Toolkit Deluxe bundled with WP Guardian, you also get the benefit of a WordPress dedicated WAF solution directly in WordPress.

 

[jmar83]

So i was right, thank you very much, then i will try it on my own website first (instead of a customer website)

What i also don't understand: How does that Plesk WP Extension communicate with Wordpress if XML RPC is disabled via WP XML disabling plugin? Directly via filesystem and database?

 

[Kaspar]

Via WP CLI mostly and for certain aspects probably directly via file system too.

 

[jmar83]

Thank you very very much!