makeDownloadLink - snipped output modifier,

Hello,
Can’t find this snipped for modifying links to be download instead of opened. It’s described in documentation but the link to the snipped doesn’t show anything http://rtfm.modx.com/display/revolution20/Input+and+Output+Filters+%28Output+Modifiers%29#InputandOutputFilters%28OutputModifiers%29-OutputModifiers

Does any one have this snipped and can share?

Thanks,
Lucas

I’m not sure I understand your request correctly, but if you mean, have pages be delivered as downloads rather than be displayed in a browser window, you need to set the [tt]content-disposition[/tt] property in the page settings tab to ’download’. You can do this with any document.

It should be added that if you have a page set to be downloaded instead of displayed in-line, it is ultimately up to the browser as to how a particular header is handled. E.g. if Chrome doesn’t have a PDF plugin installed and it encounters an "in-line" PDF Static Resource, it will download the PDF instead of opening it. Snippets don’t control how a page is handled because they aren’t controlling the headers.

OK. Than in my case ... what should I do...

I have a TV (file) that has a file name of my pdf. In my template i have [[*content]] area with text description an a link to download a PDF document: <a href="[[*TVfile]]" target="_blank">get pdf</a>.
I don’t want to change content disposition for my document to attachment because the document itself has content area with text that people want to read.
The only thing that I want to is to force download instead of opening pdf file when clicked on it.

Luke

I think we’re saying the same thing, but just to be sure... You can just create a MODx Static Resource, choose the PDF file as the source file, ensure that the content type is PDF (you may have to add your own content type), set the "content disposition" to either inline or attachment, then just link to the page (i.e. the Resource) normally as you would any other MODx page, e.g.



Where "123" is the page id of the Static Resource.

So if you’re storing a link to that resource in a TV (e.g. a TV that allows you to select another page), then you would select the Static Resource page when creating/editing pages that used that TV. Inside your template, your link would be generated by referencing the TV placeholder:



So [[*myTv]] would get converted to the page id (e.g. 123), and then the ~ placeholder would convert to that page’s URL. Make sense?

Hi Everett,
thank You for sharing Your solution. Yes Your approach will surely work, but I want to make it easier, when managing the content. Actually for each document i have text and a pdf file. It’s much easier to save pdf in TV in this document, than first crating static resource, and that linking it with that document.

But You give me one more idea that i need to somehow workout. If I can crate a static resource eg. id=123, and pass to it the value of myFileTV, and than call it in my template eg <a href="[[~123]]?content=myTv">get pdf</a> than I would not need to crate static resources for each of my pdf that are alredy stored on server in myTv.

If You have any idea how to pass value of myTv to content of static resource please advise. I’ll still try to find a way to do it.

Regards,

Lucas.

Hmm... I don’t think what you’re thinking will work. It sounds too much like rubbing a cat backwards.

Why not do this? Create a dropdown TV, then use the @DIRECTORY binding to create a list of files in that directory, allowing the user to select one. Just make sure to only put PDFs in that directory. Then you can just link to the file directly, e.g.



You don’t really need to create Static Resources unless you need to control access to those files and/or associate additional meta data with them.

Quote from: Everett at Jul 01, 2011, 10:49 PM

You don’t really need to create Static Resources unless you need to control access to those files and/or associate additional meta data with them.

Yes, that’s my case I need to set headers to force download instead of opening the file.

Good catch on the docs there - either the example needs to be changed, or a snippet added somewhere.

What a snippet like that would need is:
- a connector/resource that triggers the download (securely, not allowing to download files like core/config/config.inc.php for example )
- create a link to that connector/resource.

Let’s assume all your downloadable files are in assets/downloads. I think that if you set one resource with content disposition: attachment, give it a blank template and in the content put a [[!Download]] snippet call, you could get away with a snippet like this:



I didn’t test this and it would probably need to be modified before being production-worthy, but perhaps it can help you figure out how to make this work.

force download instead of opening the file.

You don’t have full control over that: the browser gets final say. So if you have a PDF and you want to force a download so you set it to content-disposition of "attachment", I’ve still have some browsers open it up in-line. I’d say it’s a lot easier to offer links to the files directly and leave it to the browser to open or download. The users can always do a "Save As" if the browser opens it up in-line.