Deleted Includes Folder

Hi everyone, hope I have posted in the right place. We have been in the process of upgrading our store from 1.3.9 to 1.5.0, using a second domain for testing.

In the last processes of changing the SSL settings in the configure.php files before transferring them to our main domain, both includes files (public_html/includes and public_html/admin/includes) suddenly disappeared... A bit of a shock

We are comfortable enough restoring from backups (though it is definitely annoying) but are worried that this could happen again. So, I was just wondering, does anyone have any ideas how this has happened and how it could be avoided in future.

Two of us have been working on the upgrade, both on Mac OSX and using Filezilla.

AlexSC:

Two of us have been working on the upgrade, both on Mac OSX and using Filezilla.

Just guessing, but I don't think that's ever a good idea. I've never seen this question asked before, so I'm thinking one of you accidentally deleted the folder.

stevesh:

Just guessing, but I don't think that's ever a good idea. I've never seen this question asked before, so I'm thinking one of you accidentally deleted the folder.

Thanks for the reply. We did wonder this, and it's definitely something I could accept as a possiblity, but was is odd is that both includes files were deleted. A mistake could account for one, but it would be very odd for both.

To clarify we are working in the same office, my partner has been doing the majority of the work, but I have changed a bit of CSS, images, etc here and there (nothing complex). In future we could only have one FTP client connected if you think this is a bad idea..

A 'mysterious deletion' of files or folders will not specifically be a result of having multiple FTP clients open at once.

DrByte:

A 'mysterious deletion' of files or folders will not specifically be a result of having multiple FTP clients open at once.

Thank you for the clarification.

Have restored from backup and all is running smoothly. Since it doesn't seem to be a known issue, I'm going to just chalk it up to being a really odd mistake/glitch.