comment on

I named the files with an extension so my text editor knows what "type" they are, and I'm used to files having extensions. And BTW, I do use ".perl" as an extension for perl programs.

The /gallery location you cite causes big problems because all the .js and .css files get processed too! The download code is fancier than the article's version. So /gallery gets changed to (just) gallery/images and my cite-wide LocationMatch for .html files.

The reason to handle all files in this subdirectory is because URI's will be generated for image file names with query strings, and that will pick up the real file from a different directory and resize it. I normally don't have Mason process .JPG files, and only want to turn that on in this special directory.

So, if I change that back to /gallery, how do I exclude the gallery/css and other subdirectories?

I can see in my own design I should learn this lesson and not mix up the virtual directories (gallery/Vacation/June/...) and its implementation file directories (gallery/js, gallery/css).

—John

In reply to Re^2: Mason newbe question by John M. Dlugosz
in thread Mason newbe question by John M. Dlugosz

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks