Extension Updates: WordPress Toolkit 2.0.1

Created:

2017-04-03 12:39:23 UTC

Modified:

2017-04-03 12:39:23 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Extension Updates: WordPress Toolkit 2.0.1

27 March 2017

Extension Updates

WordPress Toolkit 2.0.1

  • [-] A WordPress instance installed via the Application Catalog had a database prefix marked as non-secure. (EXTWPTOOLK-463)
  • [-] Automatic login to WordPress failed if the instance was installed using non-secure HTTP and the “Permanent SEO-safe 301 redirect from HTTP to HTTPS” option was enabled in the hosting settings of the domain. (EXTWPTOOLK-462)
  • [-] If an URL of a cloned WordPress instance ended with a slash after registering the instance in WordPress Toolkit, this URL did not change to a new one after cloning. (EXTWPTOOLK-461)
  • [-] A page for managing a WordPress instance could not be opened in WordPress Toolkit if the instance used an external MySQL server database not registered in Plesk. (EXTWPTOOLK-460)
  • [-] Slashes were present at the end of the URL of a WordPress instance installed via the Applications Catalog. (EXTWPTOOLK-458)
  • [-] WordPress could not be installed if proc_open was disabled in a domain’s PHP settings. (EXTWPTOOLK-455)
Have more questions? Submit a request
Please sign in to leave a comment.