I'm using this module( 6.x-1.0-alpha1) along with File Framework (have found this with both alpha5 and dev). Using a network folder on windows Vista, all files appear to be 0byte folders, and download as such. Disabling FileRelationsServer fixes this problem. I'm having issues connecting to the folders made available with this module (by type, node, group), so I can be sure what that looks like.

Also, browsing the dav folders (including type, node, group) through Firefox/Chrome/etc - the files look fine and can be downloaded. If it weren't for the ability to disable this module I'd say it was (yet another) issue with windows web folders.

Cheers,
Justin

Comments

Justin Miller’s picture

Justin Miller
he/him/his
Primary language English
Location Portland, OR
commented

Thanks for the report. I don't have a way to test Vista clients, so if you've got any ability to help there, I could better take a look at this.

When you say that disabling FileRelationsServer fixes the problem, do you mean that other WebDAV resources (from other modules) then work ok? Or what? Not following you there.

justin.hopkins’s picture

justin.hopkins commented

Yeah just like you say. When File Relations Server is disabled, DAV resources from FileServer work just fine.

jvieille’s picture

jvieille commented

I have the same problem.
I need to resaving the Taxonomy Server settings admin page after disabling FileRelationServer to fix the issue

jun’s picture

jun commented

Hi. I found that a difference in constant value was causing the issue:

at fileserver.module:18
define('FILESERVER_FILE', 'node_file');

at filerelationserver.module:23
define('FILERELATIONSSERVER_FILE', 'file');

QUICK FIX :

Change filerelationserver.module:23 into
define('FILERELATIONSSERVER_FILE', 'node_file');

This fixed the "files appearing as folders issue" for me.

Not sure there aren't more problems to find down the road since this problems points at an issue with the DAV API hooks IMHO.

I think that the safe road would be to implement taxonomy serving in File Relations Server. I might give it a shot... but this got me thinking into maybe a more DAV API friendly way to do this : #702860: Document Management : Allow DAV API Clients to specify non-root parent collection.

Best,

Jun.