We can limit revisions by using
define('WPPOSTREVISIONS', false);
or
define('WPPOSTREVISIONS', 20);

Make this available via the UI and ability to set defaults for all WP sites.

It would be great to have an option to export the WPTK "Sets" and then being able to import them in WPTK on the other servers.

For managing many WordPress installations with WP Toolkit, it would be helpful to be able to add a (searchable) text note to each instance.
Similar to labels, but just a free text field where you can insert a few lines of text.

When enabling all the WordPress Toolkit Security Measures, we should be able to specify and whitelist IP addresses in order to NOT apply the rules, this way the owner of website can access potentially sensitive files via URL without being blocked

Would save a lot of time setting up a new wordpress if we could create a set with default values we always set anyway, like not allowing comments from people who aren't login etc, time/dates, time zones etc.

The Wordpress Toolkit sets are only allowing preinstalling plugins and theme but does not allow any configurations such as site name, permalink settings or any other plugin related configurations

By default, Plesk's WordPress Toolkit should provide the option to disallow re-use of old passwords.

Please create a new sort option for Plugins, Themes with „Update available“ or „up to date“.

I offer to switch Wordpress toolkit screenshot service to use only fixed and published IPs, for security purpose.

Plesk - Wordpress Toolkit should support Roots.io Bedrock.

https://roots.io/bedrock/

It should be possible to exclude some bots from "bot protection" option in Wordpress Toolkit, for example, Semrushbot is used for seo in sites, and it should remain active, or acunetix is a security scanner and users may want to use it, whlie blocking other unwanted bots.

This idea was already mentioned on: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39722035-custom-labels-in-wp-toolkit-and-additional-filteri

And to give some ideas of what custom labels could be added:
- managed / unmanaged
- notes about who manages the site
- notes about special environments besides production / staging / ...

It would be less work to not have to look up these informations for each site and be able to just add a short custom label. For us these labels do not need to be filtered, but it would be a nice-to-have to have this addition like described in the original thread.

It is only possible to install a new WordPress instance with such options:
https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/wptoolkit-wordpress-toolkit.78685/

For example:
plesk ext wp-toolkit --install -domain-name <domain> -auto-updates true -plugins-auto-updates true -themes-auto-updates true

The other way is to manage it via Plesk GUI for existing domains:
https://support.plesk.com/hc/en-us/articles/115002224733

Please add a feature to manage all updates for existing wordpress domains via SSH/WP-CLI

Please consider adding functionality to auto-generate SSL (let's encrypt or premium wildcard SSL) for WordPress multisite custom domain names.

Localwp (https://localwp.com/) is an amazing tool for WordPress development. It integrates with two hosts, FlyWheel and WPEngine, which works amazingly well as well. You can clone an environment from the host to your local environment and upload it back to your host in a matter of a few clicks.

If there could be a Plesk integration as well, that would make the be great!!! ( https://localwp.com/host-interest/ )

Is it possible to exclude certain plugins when CloningSyncing a WP instance?

Example: customer wants to have AWS Cloudfront plugin only on live site and not on staging site. WHen they sync all plugins are copied.

Internal tracking ID: EXTWPTOOLK-5981

For now, the only way to manage WordPress Smart Updates notifications is to enable/disable them at all under Tools & Settings > Notifications > WordPress application updates.

Please add feature to manage Smart Updates notifications, particularly receiving only failed updates.

The WordPress Toolkit and Smart Updates shall register custom/premium assets like themes and plugins which aren't available on WordPress.org. Basically, if the Dashboard in the WordPress backend shows updates, the toolkit and Smart Updates should be able to recognize them and and include them into the update and test.

For example, the customer has a WordPress set with the required plugins.

And this WordPress set is defined in ServicePlans > ServicePlanName > Additional Services > WordPress Toolkit

However, after creating the subscription example.com in Domains > example.com > WordPress > Plugins can be found that plugins like Hello Dolly or Akismet Anti-Spam are also installed however they were not pre-selected.

Please add the CLI method to prevent the installation of such unnecessary for customer plugins.