Quote from: nklsf at Jul 06, 2010, 05:00 PM
Well, actually it is an empty template. I just assigned it to have the possibility to assign TVs to the ressource.
Quote from: splittingred at Jul 06, 2010, 05:29 PM
You should only have this in the Template:
So empty templates will not work with binary downloads? Is that by design? Don’t empty templates display [[*content]] by default anyway?
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
No, they don’t. You have to specify where [[*content]] goes, even in empty templates.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
-
MODX Staff
- 10,725 Posts
It can’t forward to the files, they would have to be directly accessible by the browser which would defeat the purpose of using Static Resources (i.e. security access controls, being able to keep them outside the document root of the web server, etc.).
This is working perfectly for me with both inline and attachment dispositions, in every browser I pull up. No 500 errors, so I think there must be something else causing your problems here.
-
MODX Staff
- 10,725 Posts
I still can’t reproduce this. Can anyone else reproduce the problem? Does the PDF in question happen to be UTF-8 or is it a different encoding? Can you compare the headers on successful download of the file (i.e. direct access via web server) with those that are getting a 500 error as a static resource?
Also, without spaces before or after right...? (or does revo clean this up automaticly?)
