Extension Updates: WordPress Toolkit 2.0

Created:

2017-03-27 06:34:17 UTC

Modified:

2017-04-03 12:42:37 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Extension Updates: WordPress Toolkit 2.0

23 March 2017

Extension Updates

WordPress Toolkit 2.0

  • [+] WordPress sites can now be cloned between domains or subscriptions.
  • [+] A WordPress site’s data (including files and/or database) can be synchronized with another WordPress site.
  • [+] A WordPress site can now be imported from another server. The Plesk Migrator extension is required for this functionality.
  • [+] Search engine indexing can now be enabled or disabled for a WordPress site.
  • [+] The events of creating and removing WordPress instances can now be processed by Plesk.
  • [+] It is now possible to enable debugging options for a WordPress site.
  • [*] Automatic updates can now be configured to install only the minor (security) updates.
  • [*] The WordPress instance management page was improved to display more clear and detailed information.
  • [*] The process of WordPress installation is now faster and has more detailed reporting.
  • [-] During WordPress installation, WordPress Toolkit did not check if a database with the same name and database user already exist. (EXTWPTOOLK-423)
  • [-] During installing WordPress on additional domains in Plesk for Windows, the “write/modify” permissions to the “wp-content” folder were not set automatically. As a result, images and themes of the WordPress installation could not be managed. (EXTWPTOOLK-419)
  • [-] When switching to another WordPress instance from a WordPress instance settings dialog, the list of other instances was displayed without URLs. (EXTWPTOOLK-407)
  • [-] In some cases, a confusing error message was displayed after WordPress installation was completed. (EXTWPTOOLK-343)
  • [-] If MySQL server data directory in Plesk for Windows was changed so that it differed from the location of MySQL server executable files, WordPress could not be installed. (EXTWPTOOLK-326)
  • [-] The “wp-config.php” file of a WordPress instance installed via WordPress Toolkit did not contain the “multisite” string, therefore it was inconvenient to enable multi-site WordPress. (EXTWPTOOLK-322)
  • [-] When the Keychain for API Secret Keys and WordPress Toolkit extensions were installed in Plesk for Linux, the reseller could not log in to Plesk. (EXTWPTOOLK-317)
  • [-] Two quick WordPress installations run one by one on a domain, could lead to conflicts.(EXTWPTOOLK-288)
  • [-] If an error occurred during WordPress installation, the full error description was not displayed in the maximized progress dialog. (EXTWPTOOLK-286)
  • [-] During WordPress installation, the progress dialog was initially displayed minimized without showing information about the installation, and the list of WordPress instances did not refresh after the installation completion. (EXTWPTOOLK-285)
  • [-] After renaming a domain with installed WordPress the “Site Address (URL)” parameter in WordPress was not changed. (EXTWPTOOLK-250)
  • [-] If the value of the “Preferred domain” parameter was changed for the domain with installed WordPress, the automatic log in to WordPress from the Plesk user interface failed. (EXTWPTOOLK-249)
  • [-] When access to WordPress Toolkit was restricted in Plesk configuration, an unclear error message was shown when trying to open WordPress Toolkit. (EXTWPTOOLK-237)
  • [-] The “Update” and “View details” links were displayed merged in the Themes and Plugins tabs. (EXTWPTOOLK-141)
  • [-] The “Owner” column in the list of WordPress installations contained a broken link if a subscription belonged to the Plesk administrator. (EXTWPTOOLK-33)
  • In some cases, WordPress sites were updated automatically even if automatic updates were disabled in their settings. (EXTWPTOOLK-20)
Have more questions? Submit a request
Please sign in to leave a comment.