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.

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.

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

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

Add "Search engine indexing" state for the domain into the filtering option for the list of sites (same as for "Debug").

Spam is not exciting.

There should be an option to disable WordPress Comments.

https://kinsta.com/blog/wordpress-disable-comments/

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.

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“.

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.

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

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

We'd like to auto-deploy some wordpress instances on our Plesk server. I've tested the Wordpress Toolkit, and it works great, but I have one problem : The Wordpress admin password isn't sent to the customer.

I know that we can read the password from the Plesk Interface, but I'd like our users to get their wordpress password without having them to log on into Plesk.

Please implement any solution to send the Wordpress password to the customer, e.g to get it trough the API call or to be able to sent the email notification directly from Plesk.

When being logged in as a customer in Plesk, it is possible to see the Wordpress Administrator's credentials.
It is required to hide the administrator's password for security reasons and let the customers login to WP Dashboard anly via the additional user account, added via the WP Dashboard itself.

Service plan, that deploys WordPress on another VPS
Or another mechanism, that will let you allocate not a separate space for the customer on the same server, but a separate VPS with a WordPress install with a 1 click.

Or at least give a header to click so to sort them up

Right now you can set a service plan to have WordPress or Joomla pre-installed with any new subscriptions, however the installation data such as admin usernames, passwords, site titles are randomized more so if the subscription/domain is setup via API. I think it could be nice if there was an option to install them with custom data or customize them via API. such that when installing via API, i can explicitly set the site title, admin username and passwords, database usernames and passwords etc.

Add possibility to have a pre-configured wp-admin.php file for WordPress installation for example in WordPress sets (Wordpress > Sets).