how do i provide db content in a forced download?

Quote from: doze at Aug 05, 2006, 01:07 PM

After you have created the file in your snippet, add

return $modx->sendRedirect(path/to/your/download.php?fileName=file.txt);

Then create the download.php and use this to "push" it for download (snatched from filedownload snippet by Kyle):

$filename = $_GET['fileName'];
$path = 'path/where/the/file/was/created/';

header('Pragma: private');
header('Cache-control: private, must-revalidate');
if (preg_match('#Opera(/| )([0-9].[0-9]{1,2})#', getenv('HTTP_USER_AGENT')) or
  preg_match('#MSIE ([0-9].[0-9]{1,2})#', getenv('HTTP_USER_AGENT'))) {
    header("Content-type: application/octetstream");
} else {
    header("Content-type: application/octet-stream");
}

$fp = fopen($path.$filename,"r");
$filedata=fread($fp,filesize($path.$filename));
fclose($fp);

if (preg_match('#Opera(/| )([0-9].[0-9]{1,2})#', getenv('HTTP_USER_AGENT')) or
  preg_match('#MSIE ([0-9].[0-9]{1,2})#', getenv('HTTP_USER_AGENT'))) {
    header("Content-type: application/octetstream");
} else {
    header("Content-type: application/octet-stream");
}
header("Content-Disposition: attachment; filename=".$filename);
print $filedata;

Hmm. Good. This means to do anything "manually". Why not. But why reading in the file and printing it?
Providing the filename as the URL should be sufficient, I think.

Quote from: silent at Aug 05, 2006, 03:32 PM

Hmm. Good. This means to do anything "manually". Why not. But why reading in the file and printing it?
Providing the filename as the URL should be sufficient, I think.

To prevent using download managers that bash the servers I guess..

What I was trying to intersperse in the conversation is that this should be very simple...

1. add the content type to the manager (see your Configuration, Site Settings tab, towards the bottom)
2. create a page with a (blank) template (i.e. no template) and set the content type appropriately, as well as the content disposition (also make sure the document is not cacheable, unless you only want to regenerate the content to be downloaded every once in a while, manually)
3. create a snippet that generates the content of your file and simply returns that content
4. add the snippet to the document you created’s content area --> e.g. [[MyCSVReport]]

That’s it. I’ve created completely dynamic, downloadable CSV reports this way, doc files, pdf files, you name it...

Quote from: OpenGeek at Aug 05, 2006, 03:44 PM

What I was trying to intersperse in the conversation is that this should be very simple...

...

Just tried it that way and yes I do get a result!

Snippet on a document with blank template, put a content type ( application/octet-stream for now) and configured page as ’attachment’. Few remarks though:

- I have two blank lines before my own generated content...
- every time I click on this document in the manager i get a download dialog, guess that’s the preview stuff... can it be disabled?
- the document title serves as the name of the file being pushed to the client, right?

Yes, Jason, that was exactly the way I first supposed it should work. But when I tried that, there was indeed a file-download prompted in the browser. But the content of that file was html, and the content of that html was an error message obviously intended to be displayed in the MODx-manager (backend) - wasn’t listed in my eventlog though. I didn’t understand that...
[just see that other posts came in while I’m writing, don’t know what to do right now, so I post anyway, but might delete/edit this one afterwards...]

Quote from: Avander_be at Aug 05, 2006, 04:25 PM

Snippet on a document with blank template, put a content type ( application/octet-stream for now) and configured page as ’attachment’. Few remarks though:

- I have two blank lines before my own generated content...
- every time I click on this document in the manager i get a download dialog, guess that’s the preview stuff... can it be disabled?
- the document title serves as the name of the file being pushed to the client, right?

First, what kind of content does your snippet produce? In other words, is application/octet-stream the appropriate type for content being returned by your snippet?

Yes, I always disable the Show Preview Window, under Configuration, Miscellaneous; you can always go to the preview tab if you want to see a preview in the manager, but, why? I prefer to just view the actual site outside the manager when I’m working.

And finally, the alias is used as the filename, unless it is empty, in which case a cleaned version of the pagetitle is used.

Quote from: silent at Aug 05, 2006, 04:35 PM

But the content of that file was html, and the content of that html was an error message obviously intended to be displayed in the MODx-manager (backend) - wasn’t listed in my eventlog though. I didn’t understand that...

What was the error message?

I’ve seen it with my own eyes. But, since I always provided the same filename, it has been overwritten.
And, according to a truism, "a requirement which cannot be budgeted is not a requirement" in this case I just add that "an error which cannot be reproduced is not an error". I must have done something wrong. Just forget about it, sorry

I was just looking back and found a strange thing, which, indeed I can reproduce:
Trying to find out how Avander_be’s issue might be solved I did the following:
1. created a new template which contains nothing but the placeholder [*content*]
2. created a snippet [[justtext]] with just one statement:
3. created a doc, using the new template and with a document-content of [[justtext]]
4. set that doc (in "page settings") to have the content type of "text/plain" and content disposition of "Attachment"
When I go to that doc, the browser says that there is a file to be downloaded (doc-title) as ASCII text.
And when I download it (takes quite a while), the file has the following content:

Strange, but reproduceable
EDIT: the preview of that doc shows exactly that code. When I click "edit" I see "[[justtext]]" again!

I think you would have better luck if you set your document to have a blank template.