Hello,

I would like to suggest something which could be VERY helpfull to customers which are moving their Wordpress instances between servers. Lets say you have domain.com on Server1. Then you are moving it to Server2 with Plesk and Wordpress Toolkit but domain.com is still pointing to Server1. Issue with Wordpress is that if you don't use main URL then all media files (css, images etc) are not being loaded correctly and customer can't be sure if everything will work correctly when he switch DNS settings for domain.com from Server1 to Server2.

My suggestion is that it would be great if there could be some kind of Preview switch (On/Off) called "Set preview URL as Wordpress main URL" (or something like that) where Wordpress toolkit will change Wordpress main URL in configuration table to one which is being used by preview link in Plesk.

This could solve all preview issues with Wordpress where some of wordpress instances are redirecting to main URL on site opening (so currently it would redirect user from Server2 preview URL to Server1 main URL).

What do you think about it? This is simple task which must change two URLs in Wordpress configuration table.

I'm aware that some URLs are hardcoded into templates, posts, pages etc. but generally speaking setting main URL in configuration table could solve all preview issues.

Thanks

What should this integration do?
- it should allow the sale of hosting subscriptions using a Woocommerce,
- it should be compatible with the Subscriptions plugin to charge monthly or annual payment. (https://woocommerce.com/products/woocommerce-subscriptions/)

Why You may want this integration?
- If you use Wordpress, it will be a simple and quick way to implement the payment for your hosting services.
- Woocomerce is the most popular e-commerce solution in the world. It is flexible and has a lot of integrations with other wordpress plugins. If you want to sell not only hosting, it may be a gold mine for you.

Implement VersionPress as part of your WordPress Toolkit. It uses WP-Cli and is Open Source.

By contributing to the project and having other devs already working on it, you will be able to amplify the speed of work being done.

Further, this project is the holy grail of WordPress development. People would literally flock to Plesk for this feature alone (not to mention its awesome in other ways).

Please seriously consider contacting the VersionPress Team. This Project basically takes the idea of Git integration, staging, and data syncing to the next level. Database changes are checked in to Git as text files where you can then resolve conflicts... you can literally edit the same post on two versions of the same site, and then merge the changes from both.

This would be a huge boon for Plesk and it already aligns nicely with the WordPress Toolkit... since it uses WP-CLI, you could simply make a GUI for it and help with the core code to speed up production.

Email notifications to customers are sent on every available WordPress update, that's far too much. My clients don't take them for important anymore and don't update at all. I suggest to fine tune available settings in Tools & Settings > Notifications > APS application updates (customer’s digest): Different notification options if the available update is a WordPress Core update, a plugin update or a theme update. So for example the plugin and theme update notification could be turned off for customers, but WordPress core update notifications would be still sent.

Another suggestion would be an option to cutomize the FREQUENZY (= e.g. once a week, once a month) for sent digest mails, as it was already asked for in this here (and closed as already available, but it's NOT available):

https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/6034455-stop-wordpress-toolkit-emails-going-out-every-nigh
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/6665897-wordpress-update-notification-e-mails-adjust-mai

Disable the built-in code editor adding define('DISALLOWCODEEDIT', true); in wp-config.php

Anonymize login error message because it actually tells you what is wrong (the username or the password), hooking into loginerrors with addfilter('login_errors, function() { return 'Login error'; });

Apply permission 400 (-rw-------) to wp-config.php

Change login URL avoiding the standard /wp-login.php or /wp-admin/ (pre)installing plugin "Lockdown WP Admin" or applying the same idea.

Block brute force (pre)installing plugin "Limit Login Attempts" or applying the same idea.

Mentioned plugins may be installed by default when Wordpress is installed through the APS, and may be added as an optional security measure by the Wordpress Toolkit.