Interesting accidental discovery

paul
@paul
10 years ago
4,325 posts
I use fdebug a lot when developing and by accident, I missed off the 'f'.
The variables were dumped to the screen.
That saved a bit of time opening the debug_log file.
Just posting here in case I'm not the only one who didn't know this :-)



--
Paul Asher - JR Developer and System Import Specialist

updated by @paul: 05/11/14 04:21:53PM
michael
@michael
10 years ago
7,692 posts
I remember that from ages ago now that you say it. I've not used it lately though.

My current patterns for finding what I have to work with are:
* if its PHP, put a break-point in phpstorm and refresh the page. You can see all the vars and where you are in execution all the way back up to router.php and every function in between where your at and the beginning.

* if its in a template {debug}.
paul
@paul
10 years ago
4,325 posts
I tend to develop using online servers so phpStorm breakpoints aren't available to me.
Still have the local server you helped me set up though, so might give it another try. Its just not been turned on in months ;-)


--
Paul Asher - JR Developer and System Import Specialist
SteveX
SteveX
@ultrajam
10 years ago
2,583 posts
Handy! I took the liberty of adding this as a docs comment here:
https://www.jamroom.net/the-jamroom-network/documentation/howto/1653/howto-read-the-debug-log


--
¯\_(ツ)_/¯ Education, learning resources, TEL, AR/VR/MR, CC licensed content, panoramas, interactive narrative, sectional modules (like jrDocs), lunch at Uni of Bristol. Get in touch if you share my current interests or can suggest better :)

Tags