55 results found

1. WordPress Smart Updates notifications

   For now, the only way to manage WordPress Smart Updates notifications is to enable/disable them at all under Tools & Settings > Notifications > WordPress application updates.

   Please add feature to manage Smart Updates notifications, particularly receiving only failed updates.

   2 votes

   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

2. add an ability to hide "Current password" field with Wordpress Administrator's password in Customer's panel

   When being logged in as a customer in Plesk, it is possible to see the Wordpress Administrator's credentials.
   It is required to hide the administrator's password for security reasons and let the customers login to WP Dashboard anly via the additional user account, added via the WP Dashboard itself.

   2 votes

   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

3. Sort update-able plugins/themes to top in WP Toolkit

   Or at least give a header to click so to sort them up

   2 votes

   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

4. Add a migration tool to WP Toolkit from other software installation platforms (Installatron / Softaculous)

   We've been using Installatron for ages, but WP Toolkit has become a really powerful tool over the last couple of years. While we can work on integrating our systems with WP Toolkit directly, one major obstacle is moving clients over from one system to the other - including their backups / update settings / etc.

   I'd love to find a way to make migrations over to the WP Toolkit seamless!

   2 votes

   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 the update! 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

5. "Search engine indexing" error report in WP ToolKit

   Can you please add an option to turn off error reporting for sites which have "Search engine indexing" turned off?

   I run many websites on subdomains with demo content that I don't want to index.

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

6. Monitoring, uptime and white label customer reports

   It would be nice to have:

   • Monitoring (alert if site offline or keyword does not exist)
   • Uptime (maintenance mode not included in downtime)
   • Reports (automatically generated WP-toolkit white label reports to send by email monthly to clients)
   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 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

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

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

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

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

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

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

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

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

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