Has anyone else had a problem with the new httpd.conf format created by easyapache3 with regards to running mod_auth_mysql? In the olden days, It was a simple installation with LoadModule mysql_auth_module libexec/mod_auth_mysql.so located at the end of the LoadModule list and then AddModule mod_auth_mysql.c Placed at the very top of the AddModule list, directly under ClearModuleList. These locations are critical if you want to use mod_auth_mysql but still retain the use of other authentication methods. If mod_auth_mysql is loaded last, it will kill all other forms of authentication. Unfortunately, with the new insanely disorganized and confusing httpd.conf format, I haven't got the slightest idea what's going on anymore and ClearModuleList is no longer used, so I can't correctly order the modules to make things work like they did in the past. The vast majority of the include files that are allegedly used to dynamically construct the working httpd.conf don't actually exist or are completely empty, so I don't have any reference points to work with. So my question is this: Is it possible to somehow control the loading order of Apache add-on modules with the new httpd.conf format? I really need to have standard .htpasswds style Basic auth as well as mysql auth working together on the same machine and the only way to accomplish that is to load mod_auth_mysql first.