{ "uuid": [ { "value": "8fc3bdab-fbfc-45f5-a397-a8f067c21c3d" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-11T06:09:49+00:00" } ], "revision_uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "revision_log": [], "status": [ { "value": true } ], "uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "title": [ { "value": "Stepping back into debugging" } ], "created": [ { "value": "2024-04-30T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T06:09:49+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2024\/04\/30\/stepping-back-into-debugging", "langcode": "en" } ], "body": [ { "value": "\n

In PHP, we have functions like var_dump()<\/code>, dump()<\/code> and dd()<\/code> that are used to debug code and print output to the screen.<\/p>\n\n

In Drupal, we have functions like dpm()<\/code> and kint()<\/code>, too.<\/p>\n\n

These functions are great for simple debugging but sometimes I need more, which is when I reach for a step debugger - namely, Xdebug.<\/p>\n\n

This is common when working in complex legacy code, where you need to be able to see a breakpoint and step through the code to see what path it takes and what the state is at each step.<\/p>\n\n

Enter Xdebug<\/h2>\n\n

Xdebug is a tool I use fairly often and something I have configured on an individual project basis.<\/p>\n\n

This week, I spent some time adding it to a new project and ensured my notes and documentation still worked.<\/p>\n\n

I use Docker and Docker Compose on Linux, so there are slight changes compared to running PHP natively, so I wanted to make sure it still works.<\/p>\n\n

I've added my latest setup to my Drupal Docker Example repository<\/a> and plan to add it to my standard Build Configs<\/a> setup for Drupal projects.<\/p>\n\n

If you use Docker Compose on Linux, it may be useful for you.<\/p>\n\n

If you haven't tried Xdebug before, I suggest giving it a try and see if improves your debugging.<\/p>\n\n ", "format": "full_html", "processed": "\n

In PHP, we have functions like var_dump()<\/code>, dump()<\/code> and dd()<\/code> that are used to debug code and print output to the screen.<\/p>\n\n

In Drupal, we have functions like dpm()<\/code> and kint()<\/code>, too.<\/p>\n\n

These functions are great for simple debugging but sometimes I need more, which is when I reach for a step debugger - namely, Xdebug.<\/p>\n\n

This is common when working in complex legacy code, where you need to be able to see a breakpoint and step through the code to see what path it takes and what the state is at each step.<\/p>\n\n

Enter Xdebug<\/h2>\n\n

Xdebug is a tool I use fairly often and something I have configured on an individual project basis.<\/p>\n\n

This week, I spent some time adding it to a new project and ensured my notes and documentation still worked.<\/p>\n\n

I use Docker and Docker Compose on Linux, so there are slight changes compared to running PHP natively, so I wanted to make sure it still works.<\/p>\n\n

I've added my latest setup to my Drupal Docker Example repository<\/a> and plan to add it to my standard Build Configs<\/a> setup for Drupal projects.<\/p>\n\n

If you use Docker Compose on Linux, it may be useful for you.<\/p>\n\n

If you haven't tried Xdebug before, I suggest giving it a try and see if improves your debugging.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "2025-05-11T06:09:49+00:00", "guid": null, "hash": "685bea9e2790b5b0bd16d23d8c64a61a", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }