Welcome Guest, Not a member yet? Register   Sign In
best way to debug CI
#11

(This post was last modified: 03-17-2021, 03:34 PM by John_Betong.)

Try using <?PHP STRICT_TYPES=1); at the start of every PHP file (it is not hereditary and only applies to that file). This ensures warnings are not “swept under the carpet”, errors are raised instead and require fixing before proceeding.

Also set error_reporting(-1):, which is maximum errors.

Only disable ini_set(‘display_errors’, ‘false’); on production to ensure both errors and warnings are logged.
Reply
#12

(01-19-2021, 05:29 PM)richb201 Wrote: I use phpStorm and xdebug and they work great together. I am debugging in a docker container too, just to make it a little more complex Smile.  A few years ago someone up on this forum recommended phpStorm, and I'd say it was one of the best decisions I have ever made. I am an IDE centric guy from way back.
Yeah, PhpStorm is very good!
Reply
#13

(This post was last modified: 05-17-2021, 11:08 PM by machoman.)

I am a newbie learning PHP and also using firephp extension it is really awesome and helping me a lot in my university project.
We love all people because life is short regards beastofapk.com forestofgames.org and nomipcgames.com
Reply
#14

nice
thanks
Reply




Theme © iAndrew 2016 - Forum software by © MyBB