It needs a possibility to change the URL or reload the correct Url of the installtion.

WordPress Permalinks are not working with Nginx.
The Webpage shows the error: wordpress 404 ngix
The URL-rewriting with other Permalinks than pageID is not working with Nginx.

Implementing this seems not easy (for me), just when you also want to use a WP caching tool.
Have a look here:

https://codex.wordpress.org/Nginx

Please implement this out of the box by activating with checkbox etc...

Thanks

I would like to see the CPU and RAM usage by Wordpress applications.

I would also like to see a warning about slow php scripts, which would help to catch Wordpress plugins that use too many resources.

It's a useful for me, to manage all my sites in one wp instance, using 3rd level domains, like mydomain.com, forum.mydomain.com, shop.mydomain.com, catalog.mydomain.com, etc.

By default, WordPress Toolkit creates instances with the same interface language as Plesk customer interface. Please consider adding the option to set custom default language for new instances.

The Wordpress Toolkit utilities in Onyx are awesome, but it would be pretty cool it could also check currently installed plugins/themes(versions) against the WPScan Vulnerability Database https://wpvulndb.com/ or some similar service so that known vulnerabilities could be highlighted, or automatically forced to be updated...

I habitually rename my wp-contents directory for security reasons (as part of iThemes Security). As a result Plesk no longer recognises the Wordpress installations on the server, when scanning so I'm unable to take advantage of Plesk's Wordpress features.

Please could this be modified to allow me to specify a custom name for my wp-contents directory?

A a reseller I would like to be able to create my own specific plug-in 'sets' for my WordPress customers. Normally this should be done at this level, not by the 'top level' administrator.

Maybe it is possible to use the same tab and visualize created sets from resellers with an icon.

It should be possible to use the WordPress commandline tool "wp-cli" via chrooted-shell.

I suggest creating an option to use Plesk API for cloning a Wordpress installation. This is well easy now in GUI environment but does not support third-party dashboard integration.

It would be great to implement this into Plesk API so clients would be able to create staging environment on one click without a need to login to the Plesk interface.

Add an option to WordPress Toolkit to disable wp-cron.php execution and optionally create a real cron job.
You would have to add:
define('DISABLEWPCRON', true);
to wp-config.php and than give the admin a choice to set up a cron job with custom times (e.g. every 10Min or 6h).

See: https://www.siteground.com/tutorials/wordpress/real-cron-job/

Possibility to log into wordpress in case of site was migrated from another server or for newly created site that is not resolved.
Currently to log into wordpress it's needed to add "IP site" to hosts file.

Allow service providers to set the number of wordpress installs possible for a client in subscription settings

The auto-update is great, but it is even better to exclude plugins from the auto-update. Some plugins breaks the site or plugins are customized.

Would be great to have WordPress plugins to be able to have restoration points on a plugin upgrade basis and not only for WordPress major upgrades.

This way, WordPress plugins can be managed individually with more control over them.

Allow reseller/customer to install wordpress (and maybe apps) via XML-API. (without APS / admin permission).