Date: Fri, 1 Feb 2019 16:40:23 +0100 From: freebsd@boosten.org To: Mark Moellering <markmoellering@psyberation.com> Cc: questions@freebsd.org Subject: Re: Problems with JSON and PHP Message-ID: <690EDED5-A1ED-41A2-BEDE-6F3EEF752838@boosten.org> In-Reply-To: <CAA0uU3X_-3cdUu6PNw4nXn2PJPFtSYF=w284wjEOBFKL-0Vj5A@mail.gmail.com> References: <C71BB378-7DC7-4C6B-83AE-21C44BA240EE@mail.sermon-archive.info> <CAA0uU3VJLXetWaeVr1CntGAnjFOyWQj0EyjB-W1ri3nJCHXeAA@mail.gmail.com> <BA63BD50-B678-4B72-82B3-8800E9C210F3@boosten.org> <CAA0uU3XR4LMBdHzTFq0tmdHmKzpsSO9F_AuMoryBrTA0%2BG2%2BFw@mail.gmail.com> <843A5A40-1344-42C0-97D8-D316D89CCCB1@boosten.org> <CAA0uU3X_-3cdUu6PNw4nXn2PJPFtSYF=w284wjEOBFKL-0Vj5A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> There you go, injecting logic. The only other thing I can think of = is >>> check the FPM php.ini file. What happens if you try a simple = json_encode >>> of a string? Try the simplest call first, then go on from there. >>> _______________________________________________ >>=20 >> The only thing I can think of is that his web server uses a different >> php.ini then the command line. >> The web server cannot find the json module. >>=20 >> Peter >>=20 >>=20 > Sorry, should have been more clear. Yes, the command line and web = server > uses different php.ini files. usually, the command line file is in a > folder marked cli and the web server file is in one marked fpm >=20 My mistake, didn=E2=80=99t read that good, apologies.=20 Digging through the php man page I found that the cli actually looks for = a php-cli.ini, if found it ignores the php.ini. OP could easily check this with =E2=80=98php =E2=80=94ini=E2=80=99 on = the cmd line. Peter=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?690EDED5-A1ED-41A2-BEDE-6F3EEF752838>