Loading Profile...
Expandrive deletes your files
2.0.1 opened a css file in cssedit, tried to save it and was told it couldn't be saved and did I want to rename it - I declined. But the bummer is my original css file has been deleted (I DID NOT DELETE IT). Where can I get the previous version?
Please don't ask me to collaborate with any testing to find your latest bug - I'm not interested - I just want a copy of the version that actually works. This has cost me a complete days work and taken a site down!!!
p.s.
One last thing before you post We've estimated the likelihood of your question getting noticed
-- What the f___
Please don't ask me to collaborate with any testing to find your latest bug - I'm not interested - I just want a copy of the version that actually works. This has cost me a complete days work and taken a site down!!!
p.s.
One last thing before you post We've estimated the likelihood of your question getting noticed
-- What the f___
I’m very angry.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Thanks for the link and sorry for being so angry online like that. Please let me know if you find/fix the bug.
All the best
Lee -
Inappropriate?We just released ExpanDrive 2.0.4b1 on the auto updater, which provides a workaround that prevents data loss using CSSEdit.
The issue roughly works like this - in hosting environments that have nested filesystems [such as a path that is a nest NFS/ZFS mount point], older version of OpenSSH based servers will not correctly rename a file using absolute pathnames when a pathname contains components from two separe filesystem. Due to limitations in the SFTP protocol, in order to rename a file over top an existing file [which is what CSSEdit does], you first need to unlink the target file. When the rename unexpectedly fails due to this server bug, the original is lost.
The fix provided in 2.0.4 will ensure that the original file contents are preserved under the original name. However, there is no way for us to provide a workaround so that saving works correctly - you will need your provider to update their server software. Please report back with any input you guys have, thanks so much for working with on this issue.
EMPLOYEE
