
Linking to private files should use 'system/files/' instead of 'sites/*/private/'.
Comment | File | Size | Author |
---|---|---|---|
#2 | linkit-private_files_direct_link-2652300-2.patch | 814 bytes | PascalAnimateur |
Linking to private files should use 'system/files/' instead of 'sites/*/private/'.
Comment | File | Size | Author |
---|---|---|---|
#2 | linkit-private_files_direct_link-2652300-2.patch | 814 bytes | PascalAnimateur |
Comments
Comment #2
PascalAnimateur CreditAttribution: PascalAnimateur commentedSimple patch that fixes the issue in my case.
Comment #3
chrisgross CreditAttribution: chrisgross commentedThis patch works for me, but from what I can tell, the path doesn't need to be absolute since 'system/files' is a valid drupal path.
Comment #4
anonWe need a test for this.
Comment #5
m.ok CreditAttribution: m.ok as a volunteer and commentedThe patch works well. But I agree with #3, because now the absolute path may cause other problems, e.g. during migration. Is it possible to use a relative path to system/files for private files?
Comment #6
dsnopekAh, I just noticed this issue, but unfortunately after creating an issue of my own:
#2922306: Direct links to private files are wrong
I got thrown off by the title on the issue because it isn't really problem that they are relative, just the way that the relative paths are generated.
The patch over on my issue fixes this problem, but in a way that keeps the private links relative.
Please let me know what you think!
Comment #7
queenvictoria CreditAttribution: queenvictoria at Holly commentedI'm using @dsnopek 's fix. Works well.