[Catalyst] Catalyst::Plugin::Static::Simple 0.11 on Win32

Andy Grundman andy at hybridized.org
Mon Nov 14 15:14:15 CET 2005


Christopher H. Laco wrote:
> When we're talking about directories outside of the Catalyst Apps root,
> I think this is a misfeature. One shouldn't have to move their content
> to allow it to be served by Catalysts static handlers. That is afterall,
> the point of this plugin.

I bet most people don't bother moving their content or use include_path.

> The directory requested was c:\images, and c:\images it should be; not
> c:\images\static...

The include_path option allows you to specify additional/alternate roots 
for static content.  So C:\images\static\1.gif would be correct.  You'd 
end up with a much larger search area if you had to look for 1.gif in 
every possible directory (root/static, root, C:\images, 
C:\images\static, and so on).  If you wanted to use C:\images\1.gif, you 
would need to refer to the file without the static directory, like:
<img src="[% c.uri_for('/1.gif') %]" />

-Andy



More information about the Catalyst mailing list