WP Toolkit - Product News

[custer]

Hi everyone!

We have released WPT v4.5, the first WPT release in 2020. Changelog:

• [+] Users can now mark their sites with one of the predefined labels (for example, Staging or Production) for easier identification.
• [+] Commercial Jetpack plugin plans can now be purchased in the plugin installation interface by end-customers. To disable this ability on the server, add jetpackPluginUpgradeEnabled = false to your panel.ini file.
• [-] WordPress Toolkit can now properly clone and Smart Update sites on Linux OSes, if their wp-config.php file is set to read-only. (EXTWPTOOLK-4216)
• [-] Database dumps created during cloning are now properly removed if database import failed during the cloning for some reason. (EXTWPTOOLK-4131)
• [-] WordPress Toolkit no longer apologetically displays [object Object] message when users are clicking on Remove to remove a site without selecting anything. (EXTWPTOOLK-4159)
• [-] Plugin and theme images in the plugin or theme installation dialogs no longer occupy much more space than allowed on Plesk Obsidian in Safari. (EXTWPTOOLK-3992)
• [-] Preview screenshots no longer occupy much more space than allowed on Plesk Obsidian in Safari. (EXTWPTOOLK-3990)
• [-] WordPress Toolkit update no longer fails due to migration package dependencies. (EXTWPTOOLK-3981)
• [-] Site counters are no longer visually glued to filter names on Updates and Security screens for several sites. (EXTWPTOOLK-3827)
• [-] Fixed several translation issues

 

[custer]

WPT v4.6 is out! Changelog:

• [+] WordPress administrators can now automatically update their website URL in the WordPress database and wp-config.php file based on the actual current URL. This procedure is particularly useful after migrating a website from a different location like your local workstation. The Update Site URL feature is available in the "hamburger" (context drop-down menu) on a WordPress site card.
• [+] CLI utility for the Clone feature was added. It can be accessed through the plesk ext wp-toolkit --clone command.
• [+] CLI utility for the Data Copy feature was added. It can be accessed through the plesk ext wp-toolkit --copy-data command.
• [-] Remote sites with modified meta tag generators can now be properly connected to WordPress Toolkit, and their WordPress version is now properly detected. (EXTWPTOOLK-4468)
• [-] It is now possible to install WordPress via CLI if the document root path is specified as / or \. (EXTWPTOOLK-4457)
• [-] WordPress administrators are no longer forced to reapply security measures due to automatic WordPress core updates flagging the site as insecure. (EXTWPTOOLK-4127)
• [-] WordPress Toolkit now works on Internet Explorer 11 because what is dead may never die. (EXTWPTOOLK-4392)
• [-] Smart Updates of WordPress Core no longer fail with the Exception: Warning: Failed to fetch checksums. Please cleanup files manually error. (EXTWPTOOLK-4195)
• [-] Interactive elements and text in the headers of the sliding screens are now much more visible even when a customized color scheme is used. (EXTWPTOOLK-3612)
• [-] Additional services added to Plesk by WordPress Toolkit are now shown properly on Plesk Obsidian. (EXTWPTOOLK-3408)
• [-] Scan operation is no longer stuck if a website with a root symlink is found. (EXTWPTOOLK-3096)
• [-] Updates check task no longer fails if a domain with a WordPress site was changed from physical hosting to something else. To tell you the truth, it has been working properly for several years, we simply didn't know for sure when exactly this bug was fixed. Well, better late than never! (EXTWPTOOLK-1042)

 

[custer]

WPT 4.7.0 was released a couple of minutes ago. Here are the changes:

• [+] WordPress Toolkit now can update paid plugins & themes, if these updates are available in the WordPress admin area. Note that certain plugins and themes do not support automatic updates, but display notifications about update availability anyway. This particulal scenario isn't fully supported yet.
• [+] WordPress administrators now have the option to disable the execution of wp-cron.php via default WordPress mechanism. Enabling this option will automatically create a regular scheduled task in Plesk, which means users can manually adjust the frequency of wp-cron.php task execution on a per-site basis.
• [+] Updates window now displays Changelog links for plugins and themes.
• [+] It's now possible to filter WordPress sites in the Installations list by their labels.
• Reduced the number of screenshot creation timeouts.
• [-] Exterminated redundant backslashes in non-English email notifications. (EXTWPTOOLK-4699)
• [-] Remote WordPress sites connected via plugin can now be properly updated again. (EXTWPTOOLK-4622)
• [-] WordPress Toolkit now works again on Windows 2012 R2, if access to Plesk via port 443 is enabled. (EXTWPTOOLK-4166)
• [-] Creation time of restore points is not updated anymore if data copy or update procedure is carried out without creating a new restore point. (EXTWPTOOLK-4115)
• [-] Updates for manually uploaded plugins and themes will now be visible in the interface if they become available in WordPress admin area. (EXTWPTOOLK-1785)

 

[custer]

WPT 4.8.0 was published several moments ago. Changes:

• [+] Server administrators can now define default WordPress installation language in the global WordPress Toolkit settings.
• [+] CLI command for enabling and disabling Smart Updates on a site was added. Run plesk ext wp-toolkit --smart-update to access it.
• Plugins and themes that require a license for automatic update will now cause a proper error message when users try to update them via WordPress Toolkit without a license.
• [-] Backup / Restore links now always lead to the corresponding subscription's Backup Manager screen. (EXTWPTOOLK-1582)
• [-] Smart Updates can now update plugins and themes uploaded manually to WordPress Toolkit if their updates were also manually uploaded to WPT. (EXTWPTOOLK-4080)
• [-] WordPress Toolkit buttons are now properly displayed in Action List if Plesk is in restricted mode. (EXTWPTOOLK-4596)
• [-] German translation for multisites was corrected. (EXTWPTOOLK-4627)
• [-] Certain manually uploaded plugins with incorrect plugin slugs no longer display a broken Changelog link. (EXTWPTOOLK-4662)
• [-] It is no longer possible to disable native wp-cron on WordPress sites that use disabled or absent PHP handler. (EXTWPTOOLK-4799)

 

[custer]

Hi everyone, here's the changelog for the freshly released WPT 4.9.0:

• [+] Server Administrators can now use Service Plans to limit the number of WordPress sites that customers can install and manage in WordPress Toolkit.
• [+] Global Settings screen now has the option to define the default database table name prefix for new WordPress installations.
• [-] It's now possible again to log in to WordPress installations after changing the access password in WordPress Toolkit and not refreshing the installation info via Refresh button or other means. (EXTWPTOOLK-5156)
• [-] Security measures are no longer applied to detached websites. (EXTWPTOOLK-5107)
• [-] Redundant backslashes in non-English email notifications from bug EXTWPTOOLK-4699 have returned from the dead and were quickly sent back packing. (EXTWPTOOLK-5042)
• [-] Websites can now be properly cloned if their scheduled task created to replace native wp-cron has no description. (EXTWPTOOLK-5033)
• [-] Update version of manually uploaded plugins and themes is now detected correctly. (EXTWPTOOLK-4966)
• [-] WordPress Toolkit working in Lite mode now correctly accepts update settings specified by users in wp-config.php file. (EXTWPTOOLK-682)

 

[custer]

Hi everyone, WPT 4.10 changelog, fresh from the oven:

• [+] Site administrators can now back up and restore individual WordPress sites using the brand new 'Back Up / Restore' functionality exclusive to WordPress Toolkit. Site backup files are included in subscription backups by default, so site administrators can use Plesk Backup Manager functionality like scheduled backups or backing up to cloud for further processing. Note: this feature isn't available on Plesk 17.8 Onyx for Windows.
• Updated and improved multiple text messages shown in the product.
• Security improvements.
• [-] Updating WordPress to version 5.5.1 does not trigger wp-cli errors anymore. (EXTWPTOOLK-5490)
• [-] Additional user accounts no longer blow up WordPress Toolkit (figuratively speaking), when accessing Plugins or Themes tabs. (EXTWPTOOLK-5219)
• [-] Server administrators now can access default plugin and theme sets on cloned Plesk installations. (EXTWPTOOLK-3132)
• [-] Change default database table prefix security measure does not fail anymore if database table has a period in its name. (EXTWPTOOLK-5376)
• [-] WordPress Toolkit no longer fails to remove one of several WordPress sites if another site under the same user account was broken in a quite specific way that we'd better not explain here for brevity's sake. (EXTWPTOOLK-5486)
• [-] Update Site URL control now works properly in List view. (EXTWPTOOLK-5037)

 

[custer]

Hey everyone, we've released WPT 5.0, check what's new:

• [+] Two words: interface update! No need to worry, though, as the new UI for managing WordPress sites is a logical evolution of the old UI based on newer technologies. Site administrators will find themselves in a fresh-yet-familiar interface with increased focus on site updates, better UX, improved performance and responsiveness.
• [+] WordPress Toolkit Lite experience (applicable for owners of Plesk Web Admin edition) has been redesigned to prettify it and make it more uniform across different screens.
• [+] The list of features available in WPT Lite was updated to make it more consistent and logical:
  • Management of Search Engine Indexing is now available for free in WPT Lite
  • Debugging management is now available for free in WPT Lite
  • Password Protection is now available for free in WPT Lite
  • Update settings for individual sites are now available for free in WPT Lite
  • Upload of plugins & themes in the plugins / themes management is now available for free in WPT Lite
  • Mass update operations (including modification of update settings for multiple sites at once) are now available only in the full (paid) version of WPT
• Starting with version 5.0, WordPress Toolkit requires Plesk Obsidian to work. Existing WordPress Toolkit installations on Plesk Onyx 17.8 will continue to function, but will no longer receive feature updates. Critical security fixes for WordPress Toolkit on Plesk Onyx 17.8 will continue to be delivered until Plesk Onyx 17.8 reaches end-of-life. We strongly recommend updating to Plesk Obsidian for the best Plesk and WordPress Toolkit experience.
• Branding of default maintenance mode template was updated. It now mentions being powered by WordPress Toolkit instead of Plesk.
• [-] Restoration of backup files no longer fails if they contain some files with read-only permissions. (EXTWPTOOLK-5561)
• [-] Websites are no longer getting stuck in maintenance mode under certain mysterious circumstances after being updated. (EXTWPTOOLK-5531)
• [-] Checkboxes are no longer missing on Security and Updates screens on Safari. (EXTWPTOOLK-5396)
• [-] Other checkboxes were not missing on Safari, but they were not aligned properly, so this was fixed as well. (EXTWPTOOLK-5367)
• [-] WordPres Toolkit now properly updates site URL when a WordPress site is hosted on a subdomain and the main domain is renamed. (EXTWPTOOLK-2268)
• [-] Smart Updates no longer compare shortcode values, avoiding certain false positives during the analysis. Shortcode names are still compared. (EXTWPTOOLK-4618)
• [-] Backup / Restore functionality is no longer displayed as available for sites connected via remote management plugin (because it was never actually available, mind you, not because we removed the feature). (EXTWPTOOLK-5446)
• [-] WordPress Toolkit now displays a helpful hint for Firefox users with enabled pop-up blockers trying to log in to WordPress via WPT. Unsurprisingly, the hint is: turn off pop-up blocker on this page if you want to log in to WordPress via WPT. (EXTWPTOOLK-5634)

 

[custer]

Hi everyone, WordPress Toolkit v5.1 is now available:

• [+] Product changelog is now accessible through the WordPress Toolkit Settings window.
• [+] (Plesk) Service plans now have the option to limit the number of backups allowed for each WordPress site.
• [+] (cPanel) Added support for an alternative "Fixed" licensing model.
• [+] (cPanel) Product translations & localization support were added.
• [+] (cPanel) Installation on CloudLinux 6 and 7 is now supported.
• [+] (cPanel) It is now possible to modify database user credentials on the Database tab of a particular WordPress site.
• [+] (cPanel) Security measure Block directory browsing was added.
• (cPanel) Site list performance in WHM was improved.
• (cPanel) WordPress Toolkit Deluxe is no longer enabled in the feature lists by default.
• [-] Website autoupdate tasks will no longer be accidentally skipped in certain rare cases. (EXTWPTOOLK-5825)
• [-] Popup window about automatic updates on the installation drawer was visited by Captain Obvious, so it can now be closed by the X (Close) button. (EXTWPTOOLK-5783)
• [-] Backup creation date is now shown with a proper timezone. (EXTWPTOOLK-5777)
• [-] Backup creation date is no longer displayed as one month in the past under certain circumstances. (EXTWPTOOLK-5776)
• [-] When Update Settings window is closed, Available Updates window no longer opens if it wasn't opened before. (EXTWPTOOLK-5673)
• [-] Smart Updates are no longer confused about what to update in certain cases when previous Smart Update run has detected issues, but update was not applied. (EXTWPTOOLK-5129)
• [-] (cPanel) Fixed the error message text displayed when unsupported PHP version is selected. (EXTWPTOOLK-5791)
• [-] (cPanel) Resellers with Make the account own itself option no longer see their own sites twice in the site list. (EXTWPTOOLK-5827)
• [-] (cPanel) WordPress Toolkit updates should now be installed automatically, as intended. (EXTWPTOOLK-5815)
• [-] (cPanel) Now you need to click account name instead of domain name to open site owner's cPanel from WHM. (EXTWPTOOLK-5732)
• [-] (cPanel) Help link now opens documentation in a separate tab or window. (EXTWPTOOLK-5720)
• [-] (cPanel) All sites registered in WordPress Toolkit no longer magically vanish from WordPress Toolkit if .wp-toolkit-identifier is changed for root or reseller. (EXTWPTOOLK-5699)
• [-] (cPanel) Initial server scan no longer fails if cPanel license was not present after WordPress Toolkit installation. (EXTWPTOOLK-5616)
• [-] (Plesk) WordPress sites on a subscription are no longer displayed as broken if access permissions of wordpress-backups directory are set to 000. On a side note, why would somebody do this?! (EXTWPTOOLK-5739)
• [-] (Plesk) Sites connected via remote plugin no longer become broken after debug is enabled. (EXTWPTOOLK-5716)
• [-] (Plesk) Purchase prompts in WordPress Toolkit Lite no longer lead users to 404 Not Found page. (EXTWPTOOLK-5682)
• [-] (Plesk) WordPress Toolkit data should now be properly restored or migrated by Plesk Migrator without the embarassing Unable to restore Plesk extension 'wp-toolkit' for subscription error. (EXTWPTOOLK-5142)
• [-] (Plesk) It is now possible to install a manually uploaded plugin or theme if the archive size is more than 12288 kB. (EXTWPTOOLK-5122)
• [-] (Plesk) Login to WordPress as admin now works after migrating WordPress site to Plesk. (EXTWPTOOLK-1581)

 

[custer]

Hello, fellow forum posters! WordPress Toolkit v5.2 is now out. Check out the changelog:

• [+] Resellers now have their own plugin and theme sets.
• [+] It is now possible to choose which theme should be activated upon the installation of a set. This functionality is available both in UI and CLI. As a bonus, similar functionality is now also available for plugins in sets.
• [+] Users will now see a visual indication next to Check Updates link if there's a Smart Update test run that was completed and is now waiting for user review.
• [+] WordPress Toolkit now fully supports plugins and themes with underscore symbol in their name. Users of js_composer plugin, rejoice!
• [+] CentOS 8 support was added.
• [+] CloudLinux 8 support was added.
• [+] Rules added by WordPress Toolkit to web server config files now have short descriptions explaining what they do.
• [+] (cPanel) A simple dashboard that lists all WordPress Toolkit Deluxe accounts was added. This dashboard can be opened from the Settings screen.
• WordPress site management interface is now expanded by default after a site is installed or cloned.
• (cPanel) Multiple performance improvements.
• [-] Checkbox for selecting all sites in the list no longer looks always selected if WordPress Toolkit license is not available. (EXTWPTOOLK-5654)
• [-] Ugly placeholder is no longer displayed in place of WordPress site title if the site was installed with empty Website title field. Now users will see a better-looking placeholder! (EXTWPTOOLK-5793)
• [-] Autoupdate settings screen no longer works in a weird way if there is more than one site in the list. (EXTWPTOOLK-5983)
• [-] Backup task no longer blows up the interface if current disk space quota is not enough to finish the backup. (EXTWPTOOLK-5784)
• [-] Smart Updates had their optimism reduced and no longer provide false negative prognosis under certain circumstances. (EXTWPTOOLK-6024)
• [-] Smart Updates no longer confuse what exactly needs to be updated during mass updates if Updates screen was refreshed after item selection. (EXTWPTOOLK-5761)
• [-] Unclear error sometimes shown during a failed installation of a WordPress site finally became a pretty clear error after all. (EXTWPTOOLK-5133)
• [-] (cPanel) WordPress Toolkit now properly uses session locale settings, displaying the interface in the expected language. (EXTWPTOOLK-5818)
• [-] (cPanel) Renaming user account via Rename prefixed databases and database users option now properly updates database prefix of WordPress sites installed in subdirectories. (EXTWPTOOLK-5632)
• [-] (cPanel) WordPress Toolkit Deluxe is no longer incorrectly disabled in the default feature list during WordPress Toolkit update, if it was enabled before. (EXTWPTOOLK-5893)
• [-] (cPanel) It is now possible to create a new domain in cPanel with WordPress Toolkit on CloudLinux 7 if there are more than, uhh, 1280 domains on the server. (EXTWPTOOLK-5989)
• [-] (cPanel) Site administrator email is now generated using parent domain name during WordPress installation on a wildcard domain via CLI. (EXTWPTOOLK-5618)
• [-] (cPanel) Server administrators will no longer be annoyed by the no packages marked for update email message on a daily basis. (EXTWPTOOLK-6009)
• [-] (cPanel) WordPress Toolkit now can be installed if tty is required in /etc/sudoers defaults. (EXTWPTOOLK-5876)
• [-] (Plesk) Infinite redirection no longer occurs when opening website if preferred domain was changed after WordPress installation. (EXTWPTOOLK-478)

 

[custer]

Hi everyone, WordPress Toolkit v5.3 is out! Changelog:

• [+] The wp-cli utility was updated to the latest version, so WordPress Toolkit now works on PHP 8. Yay! On the other hand, minimum PHP version supported by WordPress Toolkit is now PHP 5.4, so websites working on PHP 5.2 and PHP 5.3 cannot be managed by WordPress Toolkit anymore.
• [+] WordPress Toolkit now supports new autoupdate defaults introduced in WordPress 5.6. Autoupdate settings on new WP 5.6 installations are now set to "major and minor updates" by default. Existing WordPress installations updated to version 5.6 will keep their previous autoupdate settings.
• [+] New WordPress 5.6 installations managed by WordPress Toolkit are not using the WP_AUTO_UPDATE_CORE constant for configuring autoupdate settings anymore. Existing WordPress installations updated to 5.6 will keep the constant in wp-config.php file until autoupdate settings are changed. The only exception to both these cases is complete disabling of all autoupdates, which will still require WordPress Toolkit to add the constant to wp-config.php.
• [+] WordPress Toolkit now identifies and visually marks websites using unsupported version of WordPress, outdated (EOLed) version of PHP, or unsupported version of PHP.
• [+] It is now possible to clone websites with defined DEFINER clause in the database dump. If you were ever given issue ID EXTWPTOOLK-946 by our support team for tracking purposes, it's time to rejoice.
• [+] (cPanel) Server administrators can configure both cPanel and WHM upsell links for WordPress Toolkit Deluxe on the global Settings screen.
• WordPress Toolkit no longer adds WP_AUTO_UPDATE_CORE constant to wp-config.php file during operations not initiated by the customer (like checks for availability of updates, and so on). This constant will be added only after site admin has explicitly modified WordPress autoupdate settings.
• WordPress Toolkit now tries its best to create site screenshots for quarantined and otherwise unsupported sites.
• (cPanel) Default WHM upsell link for WordPress Toolkit Deluxe was updated to ensure it points to the proper destination.
• (Plesk) Site list loading speed was increased.
• [-] WordPress sites with very long rows in the database can now be properly cloned. (EXTWPTOOLK-939)
• [-] Plugins are now installed with locale matching current WordPress site locale, if possible. (EXTWPTOOLK-5167)
• [-] WordPress Toolkit can now properly work with sites that have filters and closing PHP tags in wp-config.php. (EXTWPTOOLK-4104)
• [-] It is now possible to clone sites with large database tables without encountering the Got packet bigger than 'max_allowed_packet' when dumping table error. (EXTWPTOOLK-5778)
• [-] It should now be possible to clone sites with huge (>10 GB) database tables without encountering the 504 error when opening the cloning screen. (EXTWPTOOLK-5154)
• [-] The field formerly known as Login URL had its name and hint text updated to clarify that you don't need to specify the full URL here, only the suffix. (EXTWPTOOLK-6107)
• [-] It is now possible to copy data from a site if it has files containing spaces in their names. (EXTWPTOOLK-6360)
• [-] (cPanel) WordPress Toolkit no longer fails to open in WHM with Request to backend API failed with error: Request failed with status code 504 error after multiple broken installations are found on the server. (EXTWPTOOLK-6404)
• [-] (cPanel) Cloning sites on CloudLinux servers no longer occasionally fails with Your PHP installation appears to be missing the MySQL extension which is required by WordPress error. (EXTWPTOOLK-6080)
• [-] (cPanel) WordPress Toolkit no longer fails to open in cPanel under certain rare circumstances with Failed to load WordPress Toolkit options and settings. Failed to parse response from backend, expected valid JSON error. (EXTWPTOOLK-6372)
• [-] (Plesk) WordPress Toolkit now displays a nicer error message when it cannot install the remote management plugin on a site due to upload_max_filesize restrictions on a remote server. (EXTWPTOOLK-6157)
• [-] (Plesk) Maintenance log no longer contains exceptions if there's at least one remote site connected via plugin on the server. (EXTWPTOOLK-6083)
• [-] (Plesk) Advisor measure Turn on security autoupdates can now be applied even if certain sites in the list are broken. (EXTWPTOOLK-6208)

 

[custer]

Hi everyone,

WordPress Toolkit v5.4 is finally here. Changelog:

5.4.0 (26 Apr 2021)​

• [+] WordPress Toolkit now saves a log of important actions it performs on managed websites. Logs are written in plain text and stored on each domain in the following format: /logs/wpt_action_logs/action_log_#SITE_UUID#.log
• [+] Cloning backend was fully redesigned for improved security and performance
• [+] Workflow related to wp-cron management was redesigned:
  • The option was renamed to Take over wp-cron.php to avoid the classic "enable to disable" confusion
  • It is now possible to explicitly choose if a replacement cronjob should be created or not via Create a replacement task when takeover is initiated switch
  • Replacement cronjobs are now way less strict in regards to user modifications. If WordPress Toolkit cannot find its cronjob, it will not try to recreate the cronjob, concluding that it was knowingly modified or removed by user
  • If user has butchered or removed the replacement cronjob by mistake, it can be recreated by switching off and on the corresponding Create a replacement... switch
• [+] (cPanel) Email notifications about updates and quarantined sites are now available on cPanel. There's no UI for managing them at the moment (but we're working on that!), so they are disabled by default. If you want to enable them, put the corresponding option in your config.ini file and set its value to true:
  • cpanelAdminSuspiciousInstanceNotificationEnabled - sends a notification about new suspicious instances to server administrator
  • cpanelResellerSuspiciousInstanceNotificationEnabled - sends a notification about new suspicious instances to each reseller
  • cpanelClientSuspiciousInstanceNotificationEnabled - sends a notification about new suspicious instances to each client
  • cpanelAdminAutoUpdatesNotificationEnabled - sends a digest of new available and installed updates (WordPress core, plugins, themes) to server administrator
  • cpanelResellerAutoUpdatesNotificationEnabled - sends a digest of new available and installed updates (WordPress core, plugins, themes) to each reseller
  • cpanelClientAutoUpdatesNotificationEnabled - sends a digest of new available and installed updates (WordPress core, plugins, themes) to each client
• [+] WordPress Toolkit now displays actual status of SSL/TLS support and certificate on a site card. If any issues are found, WordPress Toolkit provides a suggestion on how to fix them
• [+] Added installation state as a separate column to the CLI site list output
• [+] WordPress Toolkit now supports AlmaLinux OS on both Plesk and cPanel
• Improved pagination on website list
• Progress display in windows was standardized and unified for better experience
• Various warnings and notifications related to problematic PHP versions were improved and made more consistent
• (cPanel) Improved WHM/cPanel integration scheme for improved reliability
• Minimal WordPress version that can be installed via WordPress Toolkit was increased to WP v4.9
• [-] Cloning can now properly handle URLs with encoded forward slash in database tables. (EXTWPTOOLK-6292)
• [-] Cloning no longer fails if WordPress directories do not have proper access permissions. (EXTWPTOOLK-3089)
• [-] WordPress Toolkit no longer confuses users by telling them they have no sites installed when the site list is empty due to applied filters. (EXTWPTOOLK-6155)
• [-] The list of themes is now properly refreshed after a theme is manually uploaded and activated from the global Themes tab. (EXTWPTOOLK-4372)
• [-] It is now possible again to use Log in functionality in Safari running on iOS devices. (EXTWPTOOLK-6412)
• [-] Thanks to the new ghostbusting algorithm, orphaned tasks left by killed processes or rebooted server no longer haunt users in the interface. (EXTWPTOOLK-6326)
• [-] Default autoupdate options for minor WordPress releases starting with WordPress 5.6 are now set correctly (EXTWPTOOLK-6579)
• [-] (cPanel) WordPress Toolkit log file no longer devours all disk space on a server with a lot of accounts if cPanel account data contains unreadable characters. (EXTWPTOOLK-6224)
• [-] (cPanel) User-modified execution time of wp-cron.php replacement cronjob is no longer overwritten by WordPress Toolkit. (EXTWPTOOLK-6310)
• [-] (cPanel) WordPress Toolkit no longer doubles certain log entries. (EXTWPTOOLK-6436)
• [-] (cPanel) WordPress Toolkit no longer doubles certain log entries. (EXTWPTOOLK-6436)
• [-] (cPanel) Resellers can now upload plugins and themes when they manage customer websites in cPanel interface. (EXTWPTOOLK-6014)
• [-] (Plesk) WordPress Toolkit auto-updates management permission in Plesk now works properly again. (EXTWPTOOLK-6039)
• [-] (Plesk) WordPress Toolkit no longer sends email notifications about available updates after automatically installing these updates. Opinions vary on whether this was a user trolling algorithm or a split personality algorithm. (EXTWPTOOLK-6077)

 

[custer]

Hey everyone,

WordPress Toolkit v5.5 is out! Changelog:

5.5.0 (30 Jun 2021)​

• [+] WordPress Toolkit now logs every single action it performs.
• [+] Separate Smart Updates details log is now saved in the logs directory. This log is overwritten every time a new Smart Update procedure is launched.
• [+] Special interface for displaying WordPress Toolkit action logs is now accessible via Logs button on site cards. The interface includes filtering, real-time updates, and log rotation settings.
• [+] Database table prefix is now displayed on the Database tab of a site card.
• [+] Users can now hover their mouse over the website screenshot to see the date and time when it was made. Clicking the circular Refresh button in the top right corner will make a new screenshot.
• [+] New CLI command for setting or resetting WordPress administrator password is available: --site-admin-reset-password. Setting a new password is possible via environment variable.
• [+] (cPanel) Email notifications can now be managed in UI. Go to global WordPress Toolkit Settings and click Manage email notifications under the General Settings group.
• On a related note, email notifications are now sent to server administrators by default.
• Reduced the number of unnecessary screenshots made by the screenshotting service.
• Site list now loads faster, especially if you have multiple sites.
• Collapsed and expanded states of site cards are now saved per-user (technically, it's per-browser, but let's just pretend that's per-user).
• Mass operations on large number of sites now start much faster than before.
• Site card list has undergone selective cosmetic surgery. No major changes, just a bit of loving polish.
• [-] Certain WordPress sites with DEFINER clause can now be properly cloned again. (EXTWPTOOLK-7744)
• [-] Errors are now properly displayed on the cloning and data copy screens, if they happen. (EXTWPTOOLK-7597)
• [-] Logs no longer display empty plugin versions under certain circumstances. (EXTWPTOOLK-7532)
• [-] Logs no longer display empty theme versions under certain circumstances (similar problem as above, but we have a separate bug for it, so why not a separate entry, eh) (EXTWPTOOLK-7533)
• [-] WordPress Toolkit no longer states that All selected items were updated even when it couldn't update a theme due to licensing issues. (EXTWPTOOLK-7223)
• [-] Cloning to a subdomain with PHP8 no longer fails with Uncaught TypeError: unserialize(): Argument #1 ($data) must be of type string error. (EXTWPTOOLK-7374)
• [-] Cloning and data copying no longer panics when processing files with very long filenames or extensions. (EXTWPTOOLK-7745)
• [-] It's now possible to update plugins and themes that have rc string in their version. (EXTWPTOOLK-7743)
• [-] WordPress Toolkit no longer drowns in the depths of infinite recursion under certain circumstances that involve parent and child plugins. (EXTWPTOOLK-7519)
• [-] Copy data procedure no longer displays confusing message about not being able to find any matching tables when everything actually went right. (EXTWPTOOLK-7735)
• [-] (cPanel) Temporary files created during cloning and data copying are now properly deleted in all currently known cases. (EXTWPTOOLK-7675)
• [-] (cPanel) WordPress can now be properly installed by WordPress Toolkit on CloudLinux if CageFS was installed after WordPress Toolkit.(EXTWPTOOLK-7548)
• [-] (cPanel) WordPress Toolkit no longer fails to write logs for fresh cPanel accounts that do not yet have a logs directory created by the system. (EXTWPTOOLK-7694)
• [-] (Plesk) Purchase button no longer leads to 404 Not Found page. (EXTWPTOOLK-7746)

 

[custer]

Hi everyone,

WordPress Toolkit v5.6 is out! Here's the changelog:

5.6.0 (18 Aug 2021)​

• [+] Server admin now has access to server-wide plugin blocklist on the global Settings screen. Adding plugin slugs to this blocklist will prevent site admins from installing or activating these plugins via WordPress Toolkit. If these plugins are installed through other means, they will be found and deactivated by WordPress Toolkit with extreme prejudice.
• [+] Site admins can verify checksums of WordPress core files if they suspect their site is infected by malware. They can also reinstall WordPress core without affecting site content.
• [+] wp-cli utility was updated to version 2.5. All WordPress Toolkit features, including cloning, should now work properly on PHP 8. Due to this change, the minimum PHP version supported by WordPress Toolkit is now PHP 5.6, so websites working on PHP 5.4 and PHP 5.5 cannot be managed by WordPress Toolkit anymore.
• [+] wp-cli-bundle is now shipped together with wp-cli utility, providing access to many useful commands previously embedded in wp-cli itself.
• [+] Cloning and Smart Updates now properly handle popular caching plugins.
• [+] Users can see WordPress Toolkit log entries that happened before and after a filtered log entry by clicking the Show in context icon located to the right of the filtered entry.
• [+] You can now delete WordPress sites through CLI using the --remove command.
• [+] (cPanel) WordPress Toolkit now supports Ubuntu on cPanel.
• [+] (Plesk) WordPress-based sites in Dynamic List now have a WordPress tab with shortcuts to key WordPress Toolkit features.
• [+] (Plesk) WordPress Toolkit now assigns the corresponding database to a site after installation or cloning.
• Update process for multiple items now works significantly faster due to skipping many unnecessary operations, most of which are too embarrassing to mention here.
• Smart Update procedure itself also works a bit faster in a number of cases.
• Smart Update procedure now provides detailed information about which .htaccess customizations prevent it from working properly.
• Detection of PHP versions was improved for WordPress installations accessible via several different domains.
• Hotlink protection security measure wasn't really a security measure, so it was moved to a separate switch outside of the Check security window.
• Error handling and reporting related to PHP 8 was improved.
• (Plesk) Email notifications sent by WordPress Toolkit now include server hostname in message subject for easier identification.
• (Plesk) Domain management link is now named Manage domain to be less confusing.
• [-] Refresh button in the Logs window now properly works in all known cases (and probably in some unknown ones too). (EXTWPTOOLK-7996)
• [-] WordPress Toolkit no longer insidiously puts sites in endless maintenance mode under certain harmless circumstances. (EXTWPTOOLK-7957)
• [-] Smart Update procedure no longer fails with error if it isn't possible to check one of the site pages due to HTTP status code 500 error. (EXTWPTOOLK-7979)
• [-] WordPress Toolkit no longer tries to update WordPress core if autoupdate is set to minor and there's no actual update available. (EXTWPTOOLK-7863)
• [-] (Plesk) A long time ago, in a galaxy far, far away, WordPress Toolkit was showing installation IDs instead of installation names in error messages snown when a plugin couldn't be deleted. This no longer happens and we're not sure if it was a conscious stealth fix, or this bug simply died of old age. (EXTWPTOOLK-3573)
• [-] (cPanel) It is now possible to install WordPress Toolkit on a server with Turkish locale (tr_TR). (EXTWPTOOLK-7648)

 

[custer]

Hi,

WordPress Toolkit v5.7 is now available to general public. Changelog:

5.7.0 (30 Sep 2021)​

• [+] WordPress Toolkit now supports configuring automatic updates for individual plugins and themes. This covers the following changes:
  • Site-wide autoupdate policy now lets to choose between forcing all plugin or theme autoupdates (like before), or allowing every plugin and theme to use their own autoupdate settings
  • When Defined individually update policy is selected, site admins can also choose to enable autoupdates by default for all new plugins or themes installed via WordPress Tookit
  • Autoupdates for individual plugins and themes can be toggled on the respective Plugins and Themes tabs of the site card
  • New Autoupdate all plugins / themes switch added to the Plugins and Themes tabs of the site card allows toggling autoupdates for all plugins or themes on a site at once
• [+] It is now possible to log in to WordPress when the site is in maintenance mode. This behavior can be turned off via Restrict access to WordPress admin dashboard option in the Maintenance Mode settings.
• [+] Hotlink protection feature now allows site admins to configure which file extensions should be protected and which domains can be trusted.
• [+] Sets and global Plugins tabs now fully support the plugin blocklist feature.
• [+] A new email notification about blocklisted plugins disabled by WordPress Toolkit is now available.
• [+] Server admins can use CLI command --update-login-url-suffix to change login URL suffix.
• [+] (Plesk) WordPress Toolkit now shows Install WordPress link on Websites & Domains site card if there's no WordPress detected. Once a WordPress site is present, the link is changed to WordPress Toolkit.
• Updated look'n'feel of several UI components.
• WordPress Toolkit log entries created after updating WordPress Toolkit to v5.7 are accessible only via the Logs screen for now. Old log entries created before the update are still accessible in their old place via File Manager. The ability to download logs and access them via File Manager will be re-added in the next WordPress Toolkit update. Sorry for the inconvenience!
• Security improvements.
• Performance improvements (including faster site scanning process).
• [-] It's no longer possible to trick WordPress Toolkit into cloning the site into itself under certain rare circumstances. (EXTWPTOOLK-4357)
• [-] Cloning should no longer affect the clone source if it has if clauses in wp-config.php file. (EXTWPTOOLK-4213)
• [-] Cloning now works properly if clone target has common docroot with clone source. (EXTWPTOOLK-4673)
• [-] Autoupdate tasks no longer fail when running on IDN domains. (EXTWPTOOLK-8092)
• [-] WordPress sites no longer get stuck in permanent maintenance mode after site admin restores the default maintenance mode template soon after enabling maintenance mode. (EXTWPTOOLK-8047)
• [-] Cloning and data copy procedures now update all URLs and permalinks even if there's more than a thousand of them. (EXTWPTOOLK-8117)
• [-] You can delete WordPress sites that share database with other WordPress sites via the kebab menu. (EXTWPTOOLK-3067)
• [-] (Plesk) Customize button on the maintenance mode settings screen now properly directs users to File Manager. (EXTWPTOOLK-7722)
• [-] (Plesk) Smart Updates purchase button now works properly without confusing errors that mention cPanel. (EXTWPTOOLK-7747)

 

[custer]

Hi everyone,

WordPress Toolkit v5.8 is now available. Changelog:

5.8.0 (09 Dec 2021)​

• [+] WordPress Toolkit now regularly scans plugins, themes, and WordPress versions for known vulnerabilities using information provided by Patchstack service. Sites with known vulnerabilities are marked in the site list. Detailed information about found vulnerabilities is displayed in a separate tab of the Security window for each site.
• [+] WordPress Toolkit now detects modified WordPress login URL automatically, eliminating the need to specify it manually.
• [+] Blocklist feature now works with CLI operations.
• Updates are no longer checked for blocked plugins.
• Manually launched scan procedure now works much faster.
• Improved the cleanliness of Smart Updates: the procedure should not leave empty folders behind anymore.
• Improved the performance of installing and removing WordPress sites on servers with a lot of connected databases.
• Improved the performance of Action Log when working with very large log files.
• [-] Smart Update results page opened via the link in the notification email now works properly. (EXTWPTOOLK-8488)
• [-] Action log records with non-Latin characters are now properly displayed in all known cases. (EXTWPTOOLK-8427)
• [-] Cloning now properly copies index.php to a domain with modified vhost template. (EXTWPTOOLK-8244)
• [-] Innocent valid domains on Hotlink Protection Settings window are no longer marked as non-valid when an adjacent non-valid domain is removed from the list. (EXTWPTOOLK-8210)
• [-] Password protection now works for directories with ampersand in their name. (EXTWPTOOLK-6496)
• [-] Correct hint text is now shown for autoupdate settings on WordPress installation screen. (EXTWPTOOLK-8367)
• [-] Description of Turn off pingbacks security measure was updated to appease the nitpickers from our security team. (EXTWPTOOLK-8249)
• [-] Description of Block author scans security measure was also updated to appease the nitpickers from our security team. (EXTWPTOOLK-8253)
• [-] Changelog links for plugins and themes were returned on the Plugins and Themes global tabs and Updates screen. (EXTWPTOOLK-8339)
• [-] Remote sites connected via plugin can again be properly updated via WordPress Toolkit without unexpected consequences. (EXTWPTOOLK-8235)
• [-] Database table prefix is no longer modified during Copy Data procedure if Files Only option was selected. (EXTWPTOOLK-8452)
• [-] Database name link no longer leads to a broken screen. (EXTWPTOOLK-8425)
• [-] (cPanel) Enable bot protection and Block author scans security measures now work with enabled permalinks. (EXTWPTOOLK-8248)
• [-] (cPanel) WordPress Toolkit no longer fails with Error: Initial data load error: some required fields are not provided when opened from WHM interface under certain suspicious circumstances. (EXTWPTOOLK-8299)
• [-] (cPanel) Updates are no longer skipped if Directory Privacy feature is disabled via Feature Manager. (EXTWPTOOLK-8518)
• [-] (cPanel) WordPress installations located in a path containing a substring of an addon domain can now be properly registered in WordPress Toolkit. (EXTWPTOOLK-8268)
• [-] (Plesk) Autoupdate tasks are now properly processed even if database limit on a subscription is reached. (EXTWPTOOLK-8505)
• [-] (Plesk) Log Rotation button was removed from Action Log on Windows because turns out log rotation isn't actually available on Windows. (EXTWPTOOLK-8448)

 

[custer]

Hey everyone, WordPress Toolkit v5.9 is now available! Changelog:

5.9.0 (23 Dec 2021)​

• [+] WordPress Toolkit now sends email notifications upon discovering vulnerable plugins, themes, or WordPress sites. These notifications can be configured in the same place as other similar notifications.
• [+] Autoupdate policies for sites were extended to include automatic updates of vulnerable assets, and automatic disabling of vulnerable plugins.
• [-] Site vulnerability check now correctly identifies and marks assets that remain vulnerable after they were updated. (EXTWPTOOLK-8583)
• [-] Site vulnerability check no longer bothers with inapplicable sites (broken, quarantined, etc). (EXTWPTOOLK-8585)
• [-] Site vulnerability check should now display applicable fix version instead of the earliest one. (EXTWPTOOLK-8559)
• [-] Site vulnerability check (because what else it could be at this point, right?) now properly marks vulnerable assets on the site card after they are installed. (EXTWPTOOLK-8519)
• [-] Maintenance mode settings are no longer reset to default when you resize the maintenance mode settings window. (EXTWPTOOLK-8539)
• [-] Maintenance mode now properly validates large values for timers. (EXTWPTOOLK-3566)
• [-] WordPress Toolkit UI no longer vanishes without warning when user session expires. (EXTWPTOOLK-8580)
• [-] Comments in web server config file about Block access to sensitive files security measure are now properly attributed to this measure. (EXTWPTOOLK-8594)
• [-] (cPanel) Security window no longer throws an error when you try to open it under certain circumstances. (EXTWPTOOLK-8515)

 

[custer]

Hi everyone, WordPress Toolkit v5.10 is now out. Changelog:

5.10.0 (17 Mar 2022)​

* [+] WordPress Toolkit now also scans inactive plugins and themes for known vulnerabilities.
* [+] Email notifications about found vulnerabilities now include information about vulnerabilities found in inactive plugins and themes.
* [+] Warning about outdated PHP now includes link to
* [+] (cPanel) Due to changes related to detachment and scanning procedures WordPress Toolkit will execute a one-time server-wide scan after the update to version 5.10
* [-] (cPanel) Smart Updates no longer fails to detect update issues when nginx caching is enabled. (EXTWPTOOLK-8466)
* [-] WordPress Toolkit now uses correct PHP version for additional domain if docroot of this domain contains docroot of another domain. (EXTWPTOOLK-8648)
* [-] Fixed performance issues related to update availability checks on sites with detected vulnerabilities. (EXTWPTOOLK-8720)
* [-] Replaced non-working link in Smart Updates notification email with a working one. (EXTWPTOOLK-8884)
* [-] When users install plugins or themes with known vulnerabilities, a corresponding entry about their vulnerabilities will be added to the action log. (EXTWPTOOLK-8636)
* [-] WordPress v5.9 and higher can be installed on a domain with PHP 8.1. Note: the support for PHP 8.1 was introduced in WordPress itself, not WordPress Toolkit, but if you have contacted our support team about this issue and were given issue ID EXTWPTOOLK-8689, feel free to switch your PHP handler to version 8.1.
* [-] Certain localized WordPress installations can now be properly updated via WordPress Toolkit. (EXTWPTOOLK-8641)
* [-] You can now update your localized WordPress insallation to the latest version of WordPress even if it's not available in the current WordPress installation language. (EXTWPTOOLK-8623)
* [-] (cPanel) WordPress Toolkit no longer pointlessly spams cPanel error logs with locale-related errors. (EXTWPTOOLK-8862)
* [-] WordPress Toolkit can now properly detect login URL that was changed by `Perfmatters` plugin. Make sure you have updated the plugin to version 1.8.7 or higher. Special thanks to Perfmatters team for helping with this issue quickly. (EXTWPTOOLK-8565)
* [-] Inactive plugins and themes with known vulnerabilities are now marked as vulnerable in the WordPress Toolkit interface (EXTWPTOOLK-8493)
* [-] Inactive plugins and themes with known vulnerabilities can now be updated directly on the `WordPress Vulnerabilities` tab. (EXTWPTOOLK-8492)

 

[custer]

Hey everyone,

WordPress Toolkit v5.11 is out. Changelog:

5.11.0 (26 May 2022)​

• [+] Smart Updates feature was redesigned to improve the user experience, focusing on hard data instead of screenshots:
  • Detailed per-page information about found issues is now the main focus of user attention
  • Test website is now fully available for manual review until Smart Update is applied or discarded. This allows users to do in-depth validation for all important pages, including those that could not be covered by screenshots (like checkout pages and so on)
  • Smart Update checks up to 100 website pages now (was 30 pages before)
  • Smart Updates now works faster since it doesn't have to do high-quality screenshots anymore (users have access to the actual test website instead)
• [+] (cPanel) WordPress Toolkit now enables monitoring of cpanel_php_fpm service after installation or update to version v5.11.
• WordPress Toolkit v5.11.0 update cannot be installed on CentOS 6 or CloudLinux 6. If you are using these OSes, please update them to at least CentOS 7 or CloudLinux 7.
• (Plesk) Scan procedure was taught to no longer search for WordPress sites in the Recycle Bin (.trash) directory.
• [-] Vulnerability menu now correctly displays available updates for vulnerable sites after they were added by the Scan procedure. (EXTWPTOOLK-9146)

 

[custer]

Hi everyone, WordPress Toolkit v5.12 is out, changelog:

5.12.0 (01 Aug 2022)​

• [+] Added new optional security measure that disables WordPress XML-RPC (blocks all requests to xmlrpc.php).
• [+] (Plesk) Dynamic list now displays WordPress Toolkit icons in the list item headers for all domains with WordPress sites.
• [+] (Plesk) WordPress Toolkit now fully works on ARM64 architecture (currently supported by Ubuntu 20).
• Autoupdate tasks now work much faster if there are quarantined installations on the server.
• (cPanel) WordPress Toolkit no longer affects the font size of all WHM/cPanel page content.
• [-] WordPress Toolkit database inconsistencies no longer break WordPress installations list. (EXTWPTOOLK-9429)
• [-] (Plesk) Clone and Copy Data now properly work on ARM64. (EXTWPTOOLK-9174)
• [-] (Plesk) Install button is no longer missing for some users under certain circumstances. (EXTWPTOOLK-9314)
• [-] (Plesk) Wrong WordPress installations are no longer shown on Installations tab when WordPress Toolkit is opened via Search. (EXTWPTOOLK-9403)

 

[tfrank7]

Hi everyone, WordPress Toolkit v5.12 is out, changelog:

5.12.0 (01 Aug 2022)​

• [+] Added new optional security measure that disables WordPress XML-RPC (blocks all requests to xmlrpc.php).
• [+] (Plesk) Dynamic list now displays WordPress Toolkit icons in the list item headers for all domains with WordPress sites.
• [+] (Plesk) WordPress Toolkit now fully works on ARM64 architecture (currently supported by Ubuntu 20).
• Autoupdate tasks now work much faster if there are quarantined installations on the server.
• (cPanel) WordPress Toolkit no longer affects the font size of all WHM/cPanel page content.
• [-] WordPress Toolkit database inconsistencies no longer break WordPress installations list. (EXTWPTOOLK-9429)
• [-] (Plesk) Clone and Copy Data now properly work on ARM64. (EXTWPTOOLK-9174)
• [-] (Plesk) Install button is no longer missing for some users under certain circumstances. (EXTWPTOOLK-9314)
• [-] (Plesk) Wrong WordPress installations are no longer shown on Installations tab when WordPress Toolkit is opened via Search. (EXTWPTOOLK-9403)

Cool, it broke every connections with WordPress websites (100+)...

Can you check it, please?
I just logged in to our Plesks and WordPress Toolkit said if I tried to click on 'SETUP' >>

'
Unable to get site administrator settings: PHP Fatal error: Uncaught Error: Call to undefined function add_filter() in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1231) : eval()'d code:90

Stack trace:

#0 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1231): eval()

#1 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1192): WP_CLI\Runner->load_wordpress()

#2 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start()

#3 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process()

#4 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()

#5 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')

#6 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')

#7 {main}

thrown in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1231) : eval()'d code on line 90



Fatal error: Uncaught Error: Call to undefined function add_filter() in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1231) : eval()'d

Wasn't the best morning of my life

Thanks.