Re: Re: PHPINIDir directive

Aaron Bannert wrote: > > Aha, ok I see what you mean now. Is there a way to tell the difference > between multiple "peer" directives and a merged vhost directive? > We could detect this in the server merge function, but there is > no way that I know of for sending a meaningful message back to the > console/logs. Maybe we should just write a better PHPINIDir error message? > No I agree that knowledge of *where* the directive is used is required :) Maybe for right now, we should keep the behavior, which isn't ideal (but it *is* safe) and craft a better error message. Plus, this is a pretty special directive as well... :/ -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson