A bug in the app cloning process which needs addressing:
When cloning an app to the same server the cloned application folder is given a new unique name.
When cloning an app to a different server the clone process uses the source app’s folder name on the destination server. This leads to a problem if the app has previously been cloned as the destination server will already have a folder with this name. This causes the clone process to fail with an error.
Like many design agencies I have a ‘template’ application that I use for all new clients. I clone this template app and then customise for the relevant client. This clone bug means that after the first clone to a new server every subsequent clone to that same server fails. I’m forced to first clone the template app on the originating server to force a unique folder name, then clone that app across to the new destination server. Long winded and laborious.
Please make the cloning process, if it encounters the ‘application name already exists’ error on the destination server then it should just generate a new unique folder name in the same way it does for same-server clones.