Kevin Bonner wrote:
> I admit we have no actively running BQ install, so does httpd.conf still
> hold site configs, or are they $INCLUDEd from somewhere else? I believe
> the RaQs used to set AllowOverride in the srm.conf file for any site that
> used FrontPage extensions. If BQ-hosted sites do not have their own .conf
> file, I would suggest running 'grep -rli AllowOverride /etc/httpd/' and
> looking in each file returned for the correct spot.
I located the file "bluequartz.conf" in /etc/httpd/conf.d directory. In it,
I added to the line:
AllowOverride AuthConfig Indexes Limit
To read:
AllowOverride AuthConfig Indexes Limit FileInfo
This allowed the Mambo .htaccess file to operate without errors. So there
is the fix.
Question: If BQ had AllowOverride set to AuthConfig, Indexes and Limit by
default, what impact would there be by allowing FileInfo to be set? What
impact would there be by setting AllowOverride to All?
> I looked at a local Mambo config and what you originally posted for the
> Rewrite rules is what I see in the .htaccess file. So...it sounds like
> finding the correct location to specify the AllowOverride setting is the
> only thing needed to resolve your problem. The error 404 you mentioned
> was a good workaround for now, but I'm not sure how to stop logging every
> page hit.
Adding FileInfo to the AllowOverride and removing the error 404 workaround
has stopped the entries in the error log when Mambo parses an SEO-friendly
URL. Thanks again for all your help, you have helped me solve this problem
in its entirety, and now new customers can install Mambo without
intervention from support.