Old version not being deleted creates problems - Envoyer

Hi,

So it seems that Envoyer thinks it is successfully purging old releases - but the folder still remains.

I discovered this when fixing a bug, and even though current had the correct code, the laravel.log in current was showing an error referring to the old directory.

Once I deleted the old directory, the problem vanished.

This brings about two questions:

1. Why is Envoyer not purging the old release, but thinks it is
2. Why would having the old version on the server create this issue, when current is linked properly to the new directory?

The only thing that I could think of is with regards to PHP-FPM. It's not being restarted by Envoyer due to the host not wanting to allow that permission.