WHen restoring a Backup it would be beneficial if you could restore it to a different domain so as not to overwrite the existing domain.

This is particularly useful as it allows you to access database / files to see what has changed since the backup was created to help identify issues/errors, but doesn't destroy the curent domain in the process.

(our existing workaround at the moment is to manually backup the database and files - restore the backup - back this up manually and then recreate it in a new subdomain, then restore the first manual backup into the original domain again. This results in a required period of downtime on the domain though, depending on how long it takes to complete the process)

I have "duplicate" websites in wordpress toolkit list, because of a manual backup I did during a hacking attempt.
So, same url, same name, but different path. One is live, the other not.

I realize that there is no easy way to see the installation path of a wordpress toolkit element !
( best way : count the website rank in the list of wordress list, : click on File Manager, see the path, browser-back, count again in the list by praying you're counting right with your finger on the screen, click on it , rename it, triple check, deleting it).

Please add file path in General Info tab of the Wordpress toolkit website !

Thank you
- Arnaud

It would be really useful to be able to rollback PHP by minor versions from the Plesk console.

I am currently having to run my website on PHP 5.6, because the auto-update from PHP 7.1.11 to 7.1.12 caused a problem with a specific plugin (NextGen Gallery) that caused 500 Errors on any page with a NextGen gallery embedded.

While I wait for the issue to be fixed, I tried using PHP 7.0.26, but that is affected by the same issue due to the update from 7.0.25. The result is that I am now forced to use PHP 5.6 because it's the only version not affected.

I searched everywhere, and contacted Plesk support and found that it's not possible to rollback PHP versions, but it would be great to be able to do this. If I could rollback to the previous minor update, i.e. from 7.1.12 to 7.1.11, or 7.0.26 to 7.0.25, the problem could be avoided while I wait for a fix.

You might think that just turning off auto-updates would help, but it really wouldn't, because we don't become aware of some issues until after we update, and then we'd need to rollback as per this request/proposal.

I have today with a Backup override my Webspace. I need it vor my Work and every Day wher the Domain is offline i lost Money.

When a User get over the Webspace Limit it will be nice to let the FTP open. So the User can fix the Problem by his own.

At Time i have the Problem that my Hoster is not aviable by Phone. My Phone is ring unlimetid by Partners what happen.

I can only wait if the Support get my eMail.

When i have a activ FTP i can fix it in seconds by my self.

But with this boring closed FTP i have houers of offline Time and brake me my Neck!

LET THE FTP OPEN!