-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data destructive bug with "Make Alias In..." action! #1547
Comments
Submitted a potential fix. Now let's hope someone has time to test and merge it. 😃 I just saw @pjrobertson a minute ago. |
Closed 💃 |
that was meant to be a :D ... |
Rob will get a release out tomorrow morning. Thanks for the heads up Sesquipedalian and detailed description. |
No problem, Patrick. Glad it could be resolved quickly. Thanks to both you and Rob. Jon Stovell On 2013-07-31, at 11:57 PM, Patrick Robertson notifications@github.com wrote:
|
Whoops, I always forget it's you Jon ;-) No need for thanks my way. I just clicked the big green button. Rob did all the work :D On 1 Awst 2013, at 12:09, Sesquipedalian notifications@github.com wrote:
|
Problem description
In version 1.0.1, if the "Make Alias In..." action is used to create an alias file in the same directory as the original file that the alias is supposed to point to, the original file is overwritten with the alias file.
I recommend that a fix for this bug should be pushed out right away, since it can instantly, silently, and unexpectedly destroy user data.
Example
[First pane:] ~/Desktop/testfile.txt
[Second pane:] Make Alias In...
[Third pane:] ~/Desktop
Result: An alias file is created at ~/Desktop named testfile.txt that points to nothing but itself. The original file is gone, along with any data it contained.
Expected behaviour
What should occur is for a new alias file named "[name of original file] alias" to be created, as the Finder does.
Workaround
For now, I am disabling this action and replacing it with an AppleScript telling the Finder to make the new alias file.
Further information
The text was updated successfully, but these errors were encountered: