Fri, 10 Apr 2026 08:50:53 +0000 https://bugs.horde.org/ticket/3037 Horde_Config should validate generated PHP We can't catch _everything_, but the validate() method on ConfigForm should make sure the config file we're going to generate parses before considering the form valid. Also, to help achieve more specific error messages, we should add a new type for PHP code that also validates the individual snippets so that you can't enter something that's not valid on the right side of an = expression in one of those fields. Thu, 24 Nov 2005 16:44:01 +0000 https://bugs.horde.org/ticket/3037#t14054 > We can't catch _everything_, but the validate() method on ConfigForm > should make sure the config file we're going to generate parses > before considering the form valid. I already thought about that a few times, but this would only be possible with calling a PHP cli with the -l flag, but how to handle this gracefully with the lots of different places where it can be installed - if it is installed at all? > Also, to help achieve more specific error messages, we should add a > new type for PHP code that also validates the individual snippets so > that you can't enter something that's not valid on the right side of > an = expression in one of those fields. Wouldn't this be covered by the above? Thu, 24 Nov 2005 17:14:12 +0000 https://bugs.horde.org/ticket/3037#t14055 > I already thought about that a few times, but this would only be possible with > calling a PHP cli with the -l flag, but how to handle this gracefully with the lots of > different places where it can be installed - if it is installed at all? Well, if we assume that the worst that can happen is a parse error - as opposed to a fatal error - we could eval() it. Since we require admin access this might not be as bad a security risk as otherwise. >> Also, to help achieve more specific error messages, we should add a >> new type for PHP code that also validates the individual snippets so >> that you can't enter something that's not valid on the right side of >> an = expression in one of those fields. > > Wouldn't this be covered by the above? Other way around, really - if we lint the whole file we can't tell the user which field the error was in, if we lint each field we can. Thu, 24 Nov 2005 22:41:40 +0000 https://bugs.horde.org/ticket/3037#t14073