The CSS and JS files are loaded through the theme directories – they don’t live under public.  This is the appropriate block of the Apache configuration:


AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/css/(.*)$ /usr/local/vufind/themes/$1/css/$2

AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/images/(.*)$ /usr/local/vufind/themes/$1/images/$2

AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/js/(.*)$ /usr/local/vufind/themes/$1/js/$2

<Directory ~ "^/usr/local/vufind/themes/([0-9a-zA-Z-_]*)/(css|images|js)/">

  Order allow,deny

  allow from all

  AllowOverride All



Can you simply remove the “/vufind” part of the regular expression in the AliasMatch directives to fix the problem?


(I admit that I don’t think I’ve ever tried this, so maybe there is something more subtle at work).


- Demian


From: Chanel Wheeler []
Sent: Wednesday, November 07, 2012 1:41 PM
Subject: [VuFind-General] Correctly setting DocumentRoot for VuFind 2




I’ve just installed VuFind 2 off of Master. Has anyone successfully set up Apache so that the VuFind URL doesn’t have to contain “/vufind2”? Using the same method as I did for VuFind 1.x (with edits based on 2.0 structure) isn’t working. In particular, if I get to serve up the page, it can’t get to the CSS and JS files because they’re absolutely referenced from /usr/local/vufind2 (not /usr/local/vufind2/public).


Any ideas?





Chanel Wheeler

Library Network Programmer/Analyst

Yavapai Library Network

1120 Commerce Dr.

Prescott, AZ  86305


Phone: (928) 442-5741

Open a help desk ticket