Nope, and there doesn't appear to be any chatter about it on the web, 
so it's probably a broken Gentoo install since it seems to work 
everywhere else. Thanks -KL

Unfortunately, it looks like it hasn't.  Closing ticket.

Actually, this is starting to look more like a config. issue than a 
bug in Horde. The software upgrade coincided with a server upgrade, 
and when I rolled back to Horde 3.1.6 to do some testing, I found that 
the latest version of Gollem that works with Horde 3.1.6 now does the 
exact same thing, though it worked fine on the old server. I ran 
Gollem's test.php script and it indicated that all prerequisites are 
met. Obviously there's a failed dependency somewhere, but I'd 
appreciate a nudge in the right direction if this issue happens to 
ring a bell.

I'm not sure I understand. My VFS home directory is set in Gollem, and 
if I do this in that directory:



touch foo

ln -s foo bar



Gollem doesn't follow the symlink. It's there, but the arrow that 
usually points to the original file points to nothing, and Gollem 
doesn't follow it.

That error message indicates that the symlink's target doesn't exist. 
Have you verified that outside of Gollem?

I recently upgraded to Horde 3.3 and Gollem 1.0.4 and my VFS directory 
structure is no longer traversable because Gollem won't follow 
symlinks anymore. I get this error message:



readlink() [function.readlink]: No such file or directory



...and where my links used to look like this:



foo -> /path/to/bar



They now look like this:



foo ->



I even created a file and then created a symlink right next to it in 
the same directory, and Gollem wouldn't show the path to which the 
symlink was pointing, or follow it if clicked.



ln -s foo bar



foo

bar ->



Anything you could do to help would be much appreciated.