Scenario:
For example the specific time zone is set in Plesk > Tools & Settings > System Tine > You time zone (GMT+03:00) Europe/Sofia

However, after creating a new WordPress instance timezone will be set as UTC +0 in WordPress admin dashboard > Settings > General.

Request:
Add the ability in WordPress Toolkit use the same timezone which is set in Plesk > Tools & Settings > System Tine > You time zone or ability to set the default time zone for all newly created WordPress instances.

For now the database server assigned to the domain via service plan is used to host WordPress database. Would be nice to add ability to choose other database servers if exist as they might be more suitable for customer needs.

Please add option to delete a wordpress site via CLI. currently i can only detach.

Like the wp-cron feature released recently it would be useful to have other functionality like
- Warn if not using InnoDB
- Clear out and limit post revisions
- Disable revisions
- Cleanup autoload options
- Cleanup sessions
- Image crushing

Current version ov WP-CLI with the command plesk ext wp-toolkit --wp-cli is 1.4
the latest release is 2.4.1. please update that 3+ years old version!

thanks

Currently, WP Toolkit offers possibility to add a subdomain prefix for staging.

So, considering the main domain is "domain.tld", WP toolkit offers "staging.domain.tld" as an option.

We use a slightly different scheme, and it our setup our staging will looks like "domain.review" (note "review" instead of tld).

It will be nice to specify default staging tld (as it currently implemented for "staging" subdomain) and have possibility to use such scheme of the staging (instead of selecting the domain from the list manually)

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

For now, all the existing at "WordPress > Sets" sets are available for customers when they install WordPress.
The idea is to limit available sets in service plan, like available applications in "Applications" tab.

Add post-update hooks in WordPress Toolkit, which can be used to automate the process of committing to Git (e.g. WordPress core and plugin updates that are automatically installed by WordPress Toolkit).

Use case:

Be able to respond to the event and write a program to do things like: a) commit the changes to the local git repository and push them to origin, b) trigger an alert in the monitoring system

Currently, we can define the default database prefix, but it assigns a random table name prefix, which is confusing to users. I'd like an option to specify the default table name prefix

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.

WP toolkit should manage PHP memory limit value specified in wp-config.ph: WPMAXMEMORY_LIMIT.

This has been reported internally as requirement EXTWPTOOLK-3564.

Please, add to the "plesk ext wp-toolkit" the opportunity to uninstall WordPress from the domain

Plesk Web Admin version comes with a limited WP Toolkit.

It updates WP automatically and the option to deactivate the autoupdate is blocked because of licensing.

I understand that to handle updates from Plesk one should buy a Toolkit license but for the basic free version it should be possible do disable updates.

Thank you.

Allow configuring the Auto-Update settings of WP Toolkit based on the service plan or the Subscription.

This would allow configuring the Auto-Update settings desired to a certain amount of Subscriptions globally at once.

For example:
Service Plan 1
Update Wordpress > Yes
Update Plugins > Yes
Update Themes > Yes

Service Plan 2
Update Wordpress > Yes
Update Plugins > Yes
Update Themes > No

etc...

WordPress Instances which are not in used and considered as "broken" should be removable in WordPress Toolkit without changing wp-config.php

We manage Wordpress Sites for our Customers in different Levels, like managed Bronze-, Silver- or Gold-Level.
If we can group the Wordpress-Sites, it will be easy to select all Gold-managed Sites for Updates, Optimisations, etc.
A field for comments would also be fine.

Set WordPress admin username by default so this username is set for all the new installations.