Crap this is already resolved. I was gonna say may wish to think about this one. Some CMS systems feel it is ideal to leave the installer in place and require the user to remove it themselves. That way, if the user wants to make a copy of the installer, they can. Or, if they want to use it for a later time, they can. Some systems will also keep the installer but lock it down.

I am happy with it though. I did think maybe they'd want to go back, but on balance I thought this best. Tidiness is better. Locking is extra complexity for the user. Re-upload is easy.

There is a safeguard. The installer only deletes if you follow the link at the end of the installer. That link includes a "safe to delete flag". That way tangential calls to index.php are non-destructive.

Ahh okay that's good. I thought it was automatic as in the user didn't really have a choice.

Well they don't have a choice, just it's part of the designed flow, rather than any other arbitrary other flow.