I'm discovering this is a multi-part issue, but I'm feeling like maybe I'm missing something since what I'm attempting to build is pretty simple (a basic file browser "view" where user roles dictate view-rights to each file)

uploading "file.txt" to node #1 works great. file name is "file.txt" and if I call it in views using File: Name it matches.

uploading "file.txt" to node #2 the file is renamed (on the server) to "file_0.txt" yet when I call it up in views it still displays the file name as "file.txt"

this is a problem because, currently, to get views to display the correct private path, I have to rewrite the output of the field to "/system/files/[filename]" and therefore generating an incorrect path for node #2.

calling up File: Path in views gives the right, actual file name, but it's the wrong (files/private/) path. Same goes for when you click "Link this field to download the file."

Has anyone figured out a work around to this?
Sean

Comments

jromine’s picture

jromine CreditAttribution: jromine commented

See #575784: Views + Private Upload: Attached files: 'Link this field to download the file': does not work with private files for a suggested work-around.

rjacobs’s picture

rjacobs CreditAttribution: rjacobs commented

Unless I am missing something, it seems to me that Sean is aware of #575784: Views + Private Upload: Attached files: 'Link this field to download the file': does not work with private files and is actually highlighting a shortcoming of the work-around listed there.

I'm not sure if this should be considered a duplicate of that issue, or if this is actually a separate problem though....