DualBrowse (Finder-Remote) fails with alias in 1.8.4

[budjoe]

Have a problem with 1.8.4.
I use an alias for some folder names in the finder or on the ftp site to match names in the directory trees.
For example, my local development server may have the web root at htdocs, and the ftp site may have the web root at public_html.
An alias (either Mac or Unix Style) of public_html that resolves to htdocs on my local system would keep the local and ftp browsers in sync in 1.8.3 and previous versions.
1.8.4 does not seem to follow or link the aliases between the systems.
I do not typically synchronize, so I don't know if that is also affected.

Also just found that it fails to follow an alias on the remote system.
i.e. a remote symbolic link of a folder with permissions set correctly will not open in the ftp browser side.
in this case the folder the symbolic link points to is not within the containing folder structure. It is elsewhere on the server, but is a valid link, and follow symbolics are allowed.
This appears to have been broken on 1.8.3 also, but I hadn't used it for a while.

This was a feature that made Yummy stand out from the rest.

[JD]

Let me investigate and I'll get back to you asap.

[JD]

Ack! I think I've found the problem - wish you'd seen this a day earlier 

Working on a fix...

In the meantime, if it's crucial to your workflow, you can go back to 1.8.2 where it is working correctly. See the Yummy FTP Archive link on the Download page of the Yummy Software webiste

[JD]

Hmm, I'm not so sure, actually... 

Did you check your preferences settings? For this to work as you want it to you need to have both these settings enabled:

Resolve symlinks
Treat symlinks as normal items

... in the Server Options tab of the Preferences

With these settings enabled, it seems to behave the same as 1.8.2 for me.

[budjoe]

Found the setting in preferences, and it did solve the problem.
Thanks much.

Now if only it would follow my site symbolic link that would be great.
I can work around that, but it would be nice.
Just did a couple of tests via ssh, and there is something in the Unix permissions or ACL that is preventing this.
Guess I have to look into that a little more.

[JD]

Good I may have to make those settings enabled by default in a future update to eliminate any confusion in the future.

I'm not sure what's happening with your symlink that you can't resolve with Yummy, but it does sound like a permissions setting problem at your server rather than an issue with Yummy itself. You could check the FTP Transcript in Yummy to see what happens when it tries to resolve the symlink. Maybe that will give you a clue.