99 results found

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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 that is usually the case for CloudLinux/RHEL-downstream distributions as far as I'm aware.

   The alternative is to tell php where mysql.sock is located by adding mysql.defaultsocket = /var/lib/mysql/mysql.sock, mysqli.defaultsocket = /var/lib/mysql/mysql.sock and pdomysql.defaultsocket = /var/lib/mysql.sock either on a per-domain basis or in the main php.ini fo9r all domains (per version of php).

   I suggest adding a panel.ini setting for wpt that would allow the administrator to set their preference of localhost or 127.0.0.1 for WordPress installations.

   As an extension to this, I also suggest that in panel.ini under [php] it could be made possible to specify the default path to mysql.sock for the various libraries, just as it is currently possible to specify disable_functions settings.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank 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

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. integrate backup extensions with WP Toolkit (e.g. Google Drive)
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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 mostly fine with normal database transactions SELECT/DELETE etc but this will fail for the following scenarios

   Scenario 1: Elementor Plugin checks to see if PREFIXeevents exits and then uses an identical check !== to see if they're identical comparing against the prefix in wp-config and expected table name against what the column name is and then attempts to create the table if it's not there.

   Unix results in 7a6pcDceevents !== 7a6pcDceevents (returns false and doesn't try to create the table)
   Windows results in 7a6pcDceevents !== 7a6pcdceevents (returns true, tries to insert table and errors)

   Scenario 2: Migration from Windows to Unix, previously mixed case table names would have been changed to lowercase when creating tables but still works. However when migrated to Unix this would fail as 7a6pcDc_ doesn't equal 7a6pcdc_

   Suggestion:
   If mixed case table prefixes is still a feature, then Plesk needs to recognise what environment it's being used in, it should restrict itself on Windows to lowercase characters only or know to store the prefix value in wp-config.php (and Plesk tables) as lowercase as this is the default install settings for MariaDB in Plesk.

   If this isn't still a feature (table prefixes are all now lowercase) and/or for fixing historical installations. There also needs to be a way to remedy this problem. The prefix isn't editable via the wordpress toolkit once set and causes problems if you try to edit it from within wp-config.php

   For some reason uservoice is removing underscores from some words, apologies.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank 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

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPeter Debik (Community Manager, Plesk International GmbH) responded

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

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank 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

12. 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 themes

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank 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

13. 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 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank 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

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. 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 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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

17. 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 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  IgorG responded

    Thank 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

18. 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 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank 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

19. 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 added using the GUI to search wordpress.org for Wordfence.

    =====================================================

    plesk ext wp-toolkit --sets -operation info -set-id 9

    Set:
    ID Owner GUID Name
    9 7c5241ec-7ab7-12e9-a537-006056813f14 Standard

    Plugins:
    ID Name Slug Source Version
    11 W3 Total Cache w3-total-cache direct upload 0.9.7

    13 Wordfence Security – Firewall & Malware Scan wordfence wordpress.org latest

    As you can see, the one installed via CLI is version locked and does not count as being sourced from wordpress.org. The one installed via GUI will use the latest version from wordpress.org.

    To be clear, this feature request is asking for the ability to add a plugin to the server so that it ends up like plugin 13 in the example, not plugin 11.

    I note that Plesk Staff closed a similar Feature Request, which appears to be asking for the same thing.

    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/38062978-installing-plugins-from-wordpress-org-catalog-via

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close