Effect on other files?

[Andy Barrow]

Not sure if this is due to the the component or something else.

The web site I'm using for testing isn't very active right now, as the event has passed and we have almost a year until the next one. I was testing the component last night using the URLs. Did the Check Config and a couple of other things. It seemed to work okay.

This morning the site, and the admin panel, were not accessible. When I SSHed into the site, I found index.php, configuration.php and pretty much all other individual files in the root gone. Newly created directories like Quarantine were there.

I restored from backup and the site is working again. When I get time to do a restoration, I'll test again.

[CALUM POLWART]

Duplicate of #13.

[CALUM POLWART]

Hi Andy

I hit the same issue when J!3.5 testing last night (#13). I installed and cockily skipped the setup stages. With no SailwaveFTP folder configured it looks in the root directory for results. It then tries to process each of the of those files (so they will move to processing folder) and then because the file is not safe (i.e. it has PHP in it) it will be put in quarantine.

The solution is to NEVER use root folder for scanning. I made a fix last night which is in the next release. I'm just trying to close off two or three issues and will get a new release issued.

Processing, Quarantine etc should become sub-directories of your SailwaveFTP folder.