![]() Do not hesitate to let us know what we can further improve. This change directly resulted from user requests, so it is an excellent occasion to remind everyone that the WP Toolkit team welcomes and actively listens to constructive feedback. The Scan procedure on Plesk no longer looks for WordPress sites in the Recycle Bin (‘trash’) directory. This change was preceded by in-product warnings introduced in one of the minor WP Toolkit updates a couple of months back. We advise users of these OSes to update to at least CentOS 7 or CloudLinux 7. Additional Changesįor security reasons, WP Toolkit v5.11.0 and future updates cannot be installed on CentOS 6 or CloudLinux 6. Users can further adjust this via the ‘smartUpdateCrawlerPagesLimit’ option in the WP Toolkit configuration file. From the previous limit of 30 pages, we raised the bar to 100 pages. On the other, Smart Updates is now able to check an increased amount of site pages. On one hand, the Smart Update procedure now works considerably faster. Last but not least, there are two positive side-effects brought forward by the changes mentioned above. If Smart Updates identifies issues, they are recorded in a short list:Ĭlicking on any issue takes you to a separate tab, where all details for found issues are presented for an in-depth investigation:Īs these changes to Smart Updates were positively received during our internal UX testing phase, we sincerely hope this will equally enable a smile amongst our users. ![]() To facilitate this, users can quickly open the WordPress admin area, and access files and databases, all from a separate tab within the Smart Updates interface: This allows users to take their time, perform in-depth validation for all important pages, and include those that could not possibly be covered by screenshots (like WooCommerce checkout pages, and so on). The Test website is now fully accessible for manual review until the Smart Update is applied or discarded. After the Smart Update test procedure is finished, users are presented with a summary of the test run with (literal) emphasis put on the available access to the test site: In other words, this small detail tells you that your production site is safe while the WP Toolkit is sweating and hard at work. The ‘ Update‘ button is transformed into ‘ Run Smart Update Tests‘ to inform users that Smart Updates are enabled and will start the test run. The first changes can already be seen on the Updates screen immediately upon enabling Smart Updates: From now on, users can focus on the detailed issue report and give users the ability to access the test site for a more in-depth and personal analysis. ![]() As this was an unsatisfactory experience, we opted to implement some game-changers for the improvement of everything.Īfter several rounds of brainstorming back and forth with our Design team, we removed the screenshots altogether. As such, users did not feel comfortable when using a small bunch of static screenshots to make their decision, and it was not a walk in the park to find other, relevant information along the way. And this while the actual data about ‘identified issues’ was tucked away in a sidebar. Indeed, much of the screen estate, the space available on screen, was primarily eaten up by screenshots. ‘What are we supposed to look at?’ was one of the concerns rising to the foreground. While gathering feedback left and right, we quickly realized that Site Administrators are often still confused about how to proceed with the Smart Updates feature. That’s right, we revamped the User Experience of the Smart Updates Feature. Site administrators can now run updates with ease and breeze like never before. With the new release now available, users can expect to find the Smart Updates feature’s user experience to be significantly improved. Plesk is here with the second major WP Toolkit release of the year: v5.11.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |