Please implement a toggle in the WordPress Toolkit security section to disable / prohibit XML-RPC entirely, not just pingbacks like in the current state.

Everytime I clone an wp site from dev to prod I have to run search and replace after because the cloning feature does not automatically adjust the database urls.

It should be possible to disable the pop-up after installation of a WordPress instance with WordPress Toolkit:
"Installation Complete Wordpress has been installed. Take a minute to set it up."

At this moment, whenever a WP site is synced, the appearance of an instance at the top of the list is expected in any sort. This was done in order to make it easier to find an instance in the list.

This means the "Sort by" URL mechanism is not being respected, this change is considered a point of improvement to not cause damage to people relying on the "sort by" mechanism to distinguish their instances.

There is an export option for the "plesk ext wp-toolkit --wp-cli":

plesk ext wp-toolkit --wp-cli -instance-id 2 -- export

Starting export process...
Writing to file /var/www/vhosts/example.com/httpdocs/futureinvestments.wordpress.2022-06-03.000.xml
Success: All done with export.
But the import feature require native "wp" utility to be installed, and fails via plesk utility with error:
WordPress Importer needs to be installed. Try 'wp plugin install wordpress-importer --activate'.

Such option (import) in plesk ext wp-toolkit --wp-cli would improve usability

Add the possibility to customize the WordPress Toolkit Set to install WP in a custom directory (e.g., “/wp”) instead of installing it in the root folder (httpdocs)

Reason: The automatic WP installation performed via a WordPress Toolkit Set through a Hosting Plan would work fine if the customer’s current site is not built on WP or another php-based platform, but will fail and mess up their current site if their domain already contains a WP or php-based installation at the root level.

Create option to automatic install Wordpress Multisite domain so clients can have an easy way set up an staging environment

At this moment it is possible to have a pre-determined set of Plugins to be deployed on WP, it would be useful to also have the Ability to deploy a pre-determined copy of a WordPress website already designed

The email notification settings in Tools & Settings > Notifications should include an option to notify when a plugin is installed on a WordPress site, for security.

Add the ability to manage the default WordPress Toolkit Security Measures before setting up the instance, e.g. via some options in panel.ini.

a notes column would be helpful to make a note of where you just got to

I would suggest some custom labels like:

• Old or Deprecated
• New or Fresh (the filter returns all new sites withing a fixed date like 1 month or so)
• To be removed
• To be updated
• To be redesigned

Also:

Other label colors would also be nice like orange, red , green yellow , and grey

also commented here about filtering:

https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39722035-custom-labels-in-wp-toolkit-and-additional-filteri

Ability to change the notification frequency for site Vulnerability founds of WordPress Toolkit.

An option to restrict the installation of a deprecated WordPress versions in WPTK would be a nice addition.

Add possibility to to get a list of all plugins/themes installed across all installs.
Currently command "plesk ext wp-toolkit --plugins" only allows to get a list of manually uploaded plugins and themes

Would be nice to have an option to use "# plesk ext wp-toolkit --wp-cli" as a non-root user.

When using the WPTK "copy data" feature, it also overwrites the name of the target instance with that of the source instance. This causes both target and source instances to have the same name, which causes confusion in other operations.

Is it possible to prevent the "copy data" feature from updating the target instance's name, or remove the instance names from the UI altogether?

It would be great to be able to manage the WPTK notifications about the plugins new versions/updates to have an option to exclude the "new versions available" notificaton, when auto-updates are enabled.