What about: -------- 1. both access_compat and authz_core built shared, only authz_core loaded by default 2. use: new syntax <IfModule mod_access_compat.c> old syntax </IfModule> everywhere (including templates!) to have identical setting in new and old syntax. ------- According to that you said in comment 18, it should work if access_compat is loaded in addition to authz_core. authz_core, as the prefered one, would be unloadable only with significant change to config. For other configuration files: 1. new syntax would work always with our default conf, 2. old syntax should start to work after access_compat is loaded, 3. mix of new and old syntax would work as long as access_compat is loaded and there is not contradiction (one permits and second forbids). Both types of conditionals (comment 7, comment 18) should work. Or, am I missing SOMETHING? (In reply to Jan Matejek from comment #21) > I guess it's mostly a matter of style. Personally ISTM that having a > separate config file allows you to easily disable the whole Think of code that is not active by default (not included files, templates or commented out code). I am not saying it is not doable but _I_ would not go this way, if there is no significant advantage I have missed.