Re: GnuPG, PHP and password file
[email protected] (Rene Veerman)
| Newsgroups | php.general |
|---|---|
| Message-ID | <CACMzB5d3H3VpbJSMt_Ezm5Je5OFAcsQMbPkbcbifA5s4FKyo4Q@mail.gmail.com> |
https://www.google.com/search?q=php+turn+on+error+reporting&oq=php+turn+on+&aqs=chrome.0.0i512j69i57j0i512l5j0i22i30l3.4845j0j7&sourceid=chrome&ie=UTF-8 FTW :) On Sat, Oct 29, 2022 at 10:46 PM <[email protected]> wrote: > On Sat, 29 Oct 2022 18:06:06 +0000 > Richard <[email protected]> wrote: > > > > > > > > > > From: [email protected] > > > Sent: October 29, 2022 5:14:14 PM UTC > > > > >> On Sat, 29 Oct 2022 16:24:57 +0000 > > >> Richard wrote: > > > > >> > > >> Turn on PHP error reporting: > > >> > > >><https://www.php.net/manual/en/language.errors.basics.php> > > > > > Added error_reporting(E_ALL); at the top of the file. > > > > > > No errors reported in /var/log/apache2/error.log. > > > > Look at the sections on that page that explain displaying and logging > > [php] errors. > > I wrote an include file, 155 lines, years ago, to take care of this. It > reports errors, etc. to a php.log file. I've used it in virtually all > my projects for years. My prior statement about adding > "error_reporting(E_ALL)" was shorthand for me pasting this onto the > beginning of the file. The result was as I described-- no errors. > > Paul > > -- > Paul M. Foster > Personal Blog: http://noferblatz.com > Company Site: http://quillandmouse.com > Software Projects: https://gitlab.com/paulmfoster >