Custom md5_file Output Filter

Hi there,

I need a custom md5_file output filter or snippet but I can't find any around. I'm not a system developer unfortunately so can't make one myself

Anyone have something that I can use or even help me make one?

Thanks / T

It would be helpful to know why the default md5 output filter fails to meet your needs, and what you are trying to do.

He wants md5_file, which is different from md5, though we could definitely use more information.

I'm wondering if a regular snippet might be a better choice:






To do it as an output filter would be slower, but if you need that, you'll have to show us what the tag would look like.

Sorry for being vague guys.

My idea was to append a query parameter with the md5 output as value on those CSS, JavaScript files (chunks) that I'm editing often. Why? To get around client-side cache. The nice part with md5_file is if you decide to revert a file, users would most likely still have it cached.

Let's say I have a chunk with the following content:


I would like the output to be:


BobRay's Md5File snippet does the job. Thanks!


Idea: Would it be possible to access the HTML tag's source or href attribute and get rid of the &file parameter. It would a bit neater because the information is all-ready there so to speak. But if it is at the expense of performance I rather write it manually.

/ T

After some discussions with a colleague of mine we came up with this solution:

Chunk:


Snippet:


This way you don't have to write the file path twice.
[ed. note: tomahl last edited this post 13 years ago.]

That's a very cool idea, though I think you'd need to call it uncached for it to work:



Also, you're going to do a full hash of the entire file every time the page loads and md5_file() is not noted for its speed. This would be about 3x faster if it works on your server:



Much faster yet (for the user) would be to just append a version number manually, though if you've got a lot of files I can see why you might not want to do it that way.

Here's what I generally do:

Quote from: BobRay at Sep 20, 2013, 02:01 PM

That's a very cool idea, though I think you'd need to call it uncached for it to work:

<script src="[[!Md5File? &file=`assets/js/my.js`]]"></script>

Also, you're going to do a full hash of the entire file every time the page loads and md5_file() is not noted for its speed. This would be about 3x faster if it works on your server:

<!--?php
/* MD5File snippet */
$path = $scriptProperties['file'];
$result = split('=',exec("openssl md5 $path"));
return '/' . $path . '?build=' . $result[1]); 

Much faster yet (for the user) would be to just append a version number manually, though if you've got a lot of files I can see why you might not want to do it that way.

Here's what I generally do:

$modx--->regClientCSS($path . '?build=' . $version);

I tried to call it uncached but it made no difference. I'm not sure that is the best way of doing it anyway. At the moment I just clear the site cache after uploading all modified files and they all get a new "build" value. That way the snippet doesn't have to run on every page load..or am I wrong? Also, you think it would be better to use your snippet anyway?

Your last line of code doesn't say me much, I'm not a programmer you know. If you got the time, please show me an example of how to use it the full way.

Not being a programmer is quite frustrating when you got lot of ideas.

Thanks for support Bob.
[ed. note: tomahl last edited this post 13 years ago.]

Yes, clearing the site cache would take care of the problem and you could call it cached, which should make it much faster (though not as fast as the exec version).

As for my snippet, I'm not sure how much faster it would be, but the file's hash value would never have to be calculated. Hash methods like md5 are intentionally somewhat slow to make it harder to do a brute-force attack. My snippet would work like this:

Quote from: BobRay at Sep 20, 2013, 02:36 PM

Yes, clearing the site cache would take care of the problem and you could call it cached, which should make it much faster (though not as fast as the exec version).

As for my snippet, I'm not sure how much faster it would be, but the file's hash value would never have to be calculate. Hash methods like md5 are intentionally slow to make it harder to do a brute-force attack. My snippet would work like this:

[[AddCss? &path=`path/to/file` &version=`1.1`]]

/* Add Css snippet */
$modx->regClientCSS($scriptProperties['path'] . 
    '?build=' . $scriptProperties['version']);
return '';

My server didn't like your improved version so I'll probably stick with the one I got at the moment. It does the job.

Your last snippet would require to much manual work but that's also a handy snippet. Saving it for another day.

Thanks