1. CentOS 7 forces a "service named-chroot restart" after fresh install or named fails to work (this is even on Plesk 12 stable). I have reproduced it reliably several times and is reported elsewhere on the forums.
Our dev & QA teams are already checking this issue out, thanks!
2. Cloudflare extension fails to work, results in an "API Error" when activating sites.
We are planning to release an updated CloudFlare extension with some premium features very soon -- according to our testing, it works well in Plesk 12.5 (at least without the issue you're reporting).
3. Litespeed extension installs Litespeed and all is well until you try to start or restart litespeed then it fails.
I'll have to check it with Litespeed guys, thanks for letting us know.
4. Fresh install CentOS 7, installing Fail2Ban and ModSecurity at the same time - attempting to activate jails in Fail2Ban without visiting or saving settings in ModSecurity first results in failure to switch jails on with error output at top of page.
I've reported this to dev team, thanks!
5. Installatron extension fails with error, "Your account has no domains" when trying to install Apps
We don't have access to Installatron extension, so I can't verify this -- I'll have to contact Installatron guys and ask them about their extension (we could also add it into our extension catalog).
"Website Copying" feature is not very intuitive for WordPress installs. I don't believe it copies the database and also doesn't integrate with the WordPress toolkit. Some sort of feature would be nice to clone a WordPress install
Yeah, this is a feature we've neglected for quite some time, unfortunately. The good news is we are planning to improve this feature in the next Plesk version (the one after 12.5) -- our aim is to introduce proper cloning mechanism for websites and web apps.
7. WordPress Multisite support would be nice. The Plesk Installer seems to allow multisite out of the box for subdomain only but subdirectories are impossible as WP complains about it being an old install. How about adding selection boxes like Installatron does to enable Multisite (and per subdomain or subdirectory) on initial install?
I think it's a perfectly valid request. The only reason we are not doing it already is that Multisite WordPress doesn't seem that popular. It shouldn't be too difficult to implement, though.
8. WordPress toolkit should integrate with backups so it can automatically create a backup before updating. It's off putting there is a warning message before manually updating to backup your site first but the Automatic Update has no such warning.
That's something we have on our table for next version of Plesk as well. Moreover, we'd like to explore the possibility of making an automated rollback from pre-upgrade autobackup if upgrade goes wrong.
PS. Judging by the amount of feedback on WPT, it makes sense for me to create a survey about WordPress-related features and ask you guys what you think are the most important things missing from WPT currently. I would appreciate if you could participate in that survey too, Ross.