Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
121 results found
-
Improve the logic on how the WordPress Toolkit creates instance backup
WordPress Toolkit during backup process creates full plain copies of the database and files in the webspace before the compression. If Hard quota is enabled it is needed to have twice more allowed space otherwise it fails
2 votes -
WooCommerce Staging Process (cloning without overwriting Woocommerce content)
WooCommerce = at least 1/3 of ALL e-commerce websites use WooCommerce.
Can Plesk please make a process that works EASY for people to do the following on a WP and WooCommerce site:
Live site > Clone to Stage site > Copy to Live site
The issue is customers, orders, and products on the Live site can't be replaced/over-written, etc when you copy back to live site.
THIS PROCESS WOULD MAKE MONEY for Plesk, as for some reason, it doesn't exist anywhere, that I know of.
Please implement it :)
8 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
WP Toolkit autoupdate disabled by default
I want to disable WP Toolkit autoupdate by default, for current and future installations.
Setting "Update WordPress automatically: No" (found over a created site, or when creating a new one) by default.3 votes -
Include the option to filter or order by field "Smart Update" in WordPress > Updates.
Include the option to filter or order by field "Smart Update" in WordPress > Updates. That way customers can see every instance with Smart Update enabled to easily manage their Smart Update licenses.
6 votes -
Add notification for WP Toolkit regarding outdated PHP version
Currently, it is possible to manage WordPress Toolkit notifications regarding detected vulnerabilities in Tools & Settings > Notifications menu. This way customers are aware of issues with the instance.
However, customers are not being informed regarding the outdated PHP version in case PHP management is allowed for them. The info is only displayed in Plesk > WordPress > instance tab.2 votes -
Allow update of translations in WordPress Toolkit without need to update core
Provide to users the ability to update of translations in WordPress Toolkit without need to update core.
5 votes -
Faster deployment of Wordpress sites
Deployment or cloning of WordPress sites and then generating unique wp-admin and FTP credentials takes too many actions currently.
Ideal workflow:
1 - Enter a subdomain name (the only thing to enter) and have all other options prefilled to match the subdomain name (database name/user, FTP user, folder, etc).
2 - The site is configured automatically, including creating a subdomain, configuring SSL, creating a database/user, wp-admin user & unique password, FTP user & unique password.
3 - All credentials are displayed on the last step, allowing copy/paste, including wp-admin (user, password), and FTP (server name, port, user name, password).
1 voteHi Alex,
This will be a challenge, because it involves many different areas of configuration. We may consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-
WordPress Toolkit support for Bedrock-powered WordPress instances
Bedrock is a modern WordPress stack that implements several improvements related to WordPress setups.
Better folder structure
Dependency management with Composer
Easy WordPress configuration with environment specific files
Environment variables with Dotenv
Autoloader for mu-plugins (use regular plugins as mu-plugins)
Enhanced security (separated web root and secure passwords with wp-password-bcrypt)More information on Bedrock can be found here: https://roots.io/bedrock/
Plesk's WordPress Toolkit cannot currently handle Bedrock-powered WordPress instances.
Because some of Bedrock improvements are considered to be current best practices and provide safer setups, it would be nice to see support for Bedrock-powered instances in WordPress Toolkit.
14 votesThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
Thanks in advance!
--
IG
-
Create a setting to control which options are selected by default for newly created WordPress instances
Create a setting to control which options are selected by default for newly created WordPress instances.
For example if updates should be disabled by default.4 votes -
WordPress Toolkit security measure templates
There should be a functionality in WordPress Toolkit to manually adjust the WordPress security measures, like bot protection, to allow SemrushBot for example
5 votes -
Create plugin set
When I add a plugin to my set.
The problem can be seen in the pictures belowIs it possible, with the next update, Plugins to have icons for easier recognition ?
Thanks in advance!
Aleksandar M.4 votes -
Add Smart Update to a Service Plan
I would like to be able to add the Smart Updates feature to a specific service plan.
It wouldn’t be activated for all new installations just the users of a specific plan.
I would buy 30 sites of Smart Updates for WPT. If the new customer chooses the 'starter' plan they don't get the Smart Update, if they choose the 'super' plan then they get Smart Update for free. Free meaning it would be deducted from my quantity of sites purchased. Then it would automatically activate on their account.
I love the functionality of Smart Updates and want to make…
3 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Disable detaching the WordPress instance from the Toolkit permanently.
When the WordPress instance is detached from the WordPress Toolkit, the .wp-toolkit-ignore file appears in the Document Root directory and prevents attaching the instance back. Is it possible to disable that? I do not want to detach permanently.
3 votes -
Search and replace urls after cloning
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.
3 votes -
Disable "Install Plugins" pop-up after WordPress Toolkit instance installation
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."3 votes -
Improve WP-Toolkit "Sort by" mechanim
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.
3 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Add the import feature to the "plesk ext wp-toolkit --wp-cli" utility
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
1 voteThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Add the possibility to customize the WordPress Toolkit Set to install WP in a custom directory
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.
3 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Create option to automatic install Wordpress Multisite domain
Create option to automatic install Wordpress Multisite domain so clients can have an easy way set up an staging environment
4 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Ability to deploy a pre-determined WordPress instance for customers
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
3 votes
- Don't see your idea?