Problem with symlinks

[TJung]

Hello,

I'm using Yummy FTP 1.9.1 on Mac OS X 10.6.8.

I have conncet to a server with symlinks. The directory structure is something like this:

Code: [Select]

example01 -> subdir/example01
example02
example03
example04 -> subdir/example04
subdir
 |
 |--> example01
 |--> example04

So, example01 and example04 on the root level are symbolic links which point to the corresponding folder in "subdir".

Now, when I download them to my Mac, example01 and example04 are not created as symlinks on my hard drive, but as normal folders; i.e. when the download is complete I have the contents of example01 and example04 on my hard drive twice.
Both  /example01 and /subdir/example01 are folders, no symlinks/aliases.

So I looked at the Server Options tab of the Preferences and saw that "Resolve symlinks" is enabled, I thought: "Aaaaah", disabled it and started the download again…
only to find out that the result is exactly the same. Quitting an re-starting Yummy FTP didn't have any effect, too.

So, what's going wrong here and is there something I can do to download the symlinks and keeping them as symlinks?

Kind regards,
Tobias Jung

[JD]

Does disabling 'Treat symlinks as normal items' make it behave as you expect?

[TJung]

Sorry, where can I find this option?

I'm working with the german localisation, in the Server Options tab I see "Symbolische Links auflösen" (Resolve symlink) and "Symlinks auch in Unterordnern auflösen" (Resolve symlinks in subdirectories).
Nothing that seems to be a translation of "Treat symlinks as normal items".

[TJung]

Update:

I now tried setting english as preferred language in the OS X system prefs and restarted Yummy FTP.
Well, obviously there's a bug in the german localisation, because "Treat symlinks as normal items" really doesn't translate "Symlinks auch in Unterordnern auflösen".

I tried all four combinations of en-/disabling both options, but I always get the same results, i.e no symlinks on my hard drive.

[JD]

Sorry for the delayed reply.

Reviewing the code, symlinks like this are simply ignored on the grounds that they won't be usable on the destination system.

Why do you want them transferred and how do you expect them to behave once transferred, and potentially back again?

[TJung]

Why do you want them transferred

Well, I like to have the exact directory/file structure on my local apache as it is the remote server.
Don't know why the symlinks where created there, it's a project that's been running some time before I recently joined. And the person who was responsible before isn't available anymore.

Basically, they are used so that you can call up /example01/somefile.php in your web browser and the file /subdir/example01/somefile.php gets loaded. I don't know why they didn't use some redirect in the .htaccess file for that.

and how do you expect them to behave once transferred, and potentially back again?

I don't think that's necessary anymore:
Now, I downloaded only the "real" files (those from "subdir" in my example) and created the symlinks in OS X's terminal.

Sorry for stealing time and effort, I should've thought of this earlier!
Kind regards,
Tobias Jung