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
98 results found
-
Update a specific plugin on multiple websites from uploaded zip at once
It should be possible to use an uploaded plugin to update all the plugins on multiple websites once.
A feature is required to use the uploaded plugin to update the outdated plugins on multiple websites at once.
Also, when we click on install option on uploaded plugin it gives all websites in wp-toolkit and there is no option to sort the list to required website options to update or install the uploaded plugin.
1 vote -
make plugin pack installation able to handle dependent plugins
This feature request originated here: https://talk.plesk.com/threads/plugin-package-cannot-be-installed-premium-plugin-requires-base-plugin.371482/
The problem is that plugin X needs to be active so plugin Y can be activated. (In my case, it was the AIOS plugin with its premium version, which WP toolkit wasn't able to activate)
It seems that WP Toolkit tries to activate all plugins at once when installing a plugin pack. An option to tell WP Toolkit to enable each plugin alone in the order they were added to the plugin pack instead of all together would be useful in this case. But there are probably more ways to optimize WP toolkit for…
1 voteThank 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
-
Ability to hide security warning about disabled "Search engine indexing"
It would be nice, if this won't be defined as a problem/warning under security warnings inside WP Toolkit when you disabled "Search engine indexing"
1 vote -
WordPress Toolkit resource limit CPU/RAM for subscriptions. Or equivalent to cgroups on Linux for Windows.
WordPress Toolkit resource limit CPU/RAM for subscriptions. Or equivalent to cgroups on Linux for Windows.
1 vote -
panel.ini setting to select 127.0.0.1 or localhost for WPT WordPress installations
When using CloudLinux's alt-php versions and when using Plesk's php version management facility instead of CloudLinux PHP Selector, the default path to mysql.sock is not set, or in some cases incorrectly set to /tmp/mysql.sock.
Any php script, including WordPress, that is set to use "localhost" to connect to the database will then fail to connect. This can cause severe problems with the WordPress Toolkit.
If, instead of localhost, the host address is set to 127.0.0.1, php uses a network connection instead of trying to connect to mysql.sock, and all is well. Naturally this assumes that mysql/mariadb listens on 127.0.0.1 but…
1 voteThank 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
-
Enable 'Take over wp-cron.php' for all existing instances in WordPress
Please consider adding the functionality to enable 'Take over wp-cron.php' not only for newly create instances (WordPress > Settings > Disable wp-cron.php on all new WordPress installations) but for all existing WP instances at the same time. At the moment the wp-cron.php take over can only be done for one instance at the time. It would really improve the customer expirience if such functionality can be enabled for all existing instances at the same time.
1 vote -
Create and Save Custom WPTK View
Currently, WPTK doesn't save the settings if the amount of sites to display on the WPTK main site changes.
The default view is 10 sites, if I change to "ALL" and close the session, the next time it will go back to 10 sites.
WPTK should save the last view as currently Plesk does with other sites, like domains or customers.
1 vote -
1 vote
-
1 vote
-
wordpress toolkit table prefix mixed case fix/patch
I'm not sure if it's still the case but the toolkit used to (possibly still does) create table prefixes with mixed case characters (or this is done via the security checkup for existing tables).
Unix is case sensitive, windows is not.
MariaDB
lowercasetablename=0 default for Unix = stored as provided and case-sensitive. $tableprefix = '7a6pcDc' will be stored as 7a6pcDctablename in the DB
lowercasetablename=1 default on Windows = uppercase changed to lowercase but still case-insensitive $tableprefix = '7a6pcDc' will be stored as 7a6pcdctablename in the DB.This is…
1 voteThank you for this idea. It is a valid claim. 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
-
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 :)
3 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.2 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.1 vote -
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.
2 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.
-
Ability to disable Wordpress Toolkit check
Ability to disable WordPress toolkit check to avoid false positive and quarantine a WordPress instance that is not infected.
1 vote -
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.
2 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
-
Wordress toolkit plugin "ignore" toggle
Being able to make toolkit ignore a plugin (and themes?)
(for manually fixed abandonned plugins with published exploits)
1 vote
- Don't see your idea?