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
99 results found
-
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
-
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
-
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 -
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 -
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 -
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
-
Export list of all installed plugins and themes on all instances
Add possibility to to get a list of all plugins/themes installed across all installs.
Currently command "plesk ext wp-toolkit --plugins" only allows to get a list of manually uploaded plugins and themes1 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
-
Change WPTK target instance name when copying an instance
When using the WPTK "copy data" feature, it also overwrites the name of the target instance with that of the source instance. This causes both target and source instances to have the same name, which causes confusion in other operations.
Is it possible to prevent the "copy data" feature from updating the target instance's name, or remove the instance names from the UI altogether?
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
-
Provide WPTK with ability to manage NinjaFirewall plugin
Currently, WordPress Toolkit allows only deactivating of the plugin in
WordPress > example.com > Plugins
tab. However, it should also be possible to activate it via WPTK, not directly in WP Admin dashboard.1 vote -
Strengthen WordPress Toolkit password policy to match Plesk's password policy
WordPress Toolkit doesn't have a strict password policy as Plesk has, as it allows very weak passwords to be changed to. Therefore, allowing WordPress Toolkit to have the same password policy as configured in Plesk or having a configurable password policy should increase security.
1 vote -
WPTK Sets "Migration"
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.
1 voteWe 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
-
Add CLI command that prevents installation of the plugins that are shipped with WordPress by default
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.
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 option to select default TLD for staging
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)
1 voteThank you for your input! 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.
—
IG -
Allow Plugin sets to add plugins from wordpress.org catalog via WordPress Toolkit CLI
Please, implement a feature for adding plugins to plugin sets from wordpress.org catalog via WordPress Toolkit CLI
The CLI command 'plesk ext wp-toolkit --sets -operation add-plugin' requires a plugin to first be installed either in GUI or CLI using 'plesk ext wp-toolkit --plugins'.
The issue here is that the 'plesk ext wp-toolkit --plugins' command is currently unable to install plugins from wordpress.org in the same way that you can via the GUI.
As an example, look at this set which contains 2 plugins, one added using the command 'plesk ext wp-toolkit --plugins -operation add -source-url https://downloads.wordpress.org/plugin/w3-total-cache.0.9.7.zip'; and the other…
1 vote
- Don't see your idea?