Drupal:Debugging and tracing
Debugging & Logic Tracing
To monitor the internal "order of procedures" and database handshake:
| Method | Command | Purpose
|
|---|---|---|
| Live Stream | ./vendor/bin/drush wd-tail |
Real-time log of PHP errors, DB queries, and User actions. |
| Object Inspection | kdf($entity); |
(Requires Devel) Formats complex data objects for "ICT-Pro" inspection. |
| ECA Workflow Trace | UI -> Reports -> ECA Log | Step-by-step trace of automated Unique ID logic. |
| SQL Trace | ./vendor/bin/drush devel:query |
Lists every SQL query sent to the MariaDB Twin Server during a page load. |
Successor Debugging Protocol
- Check PHP Logs:
tail -f /var/log/httpd/drupal_error.log - Check Drupal Logs:
./vendor/bin/drush watchdog:show --severity=Error - Rebuild Cache: If logic is stuck, always run
drush crfirst.
Use code with caution.
Final Professional Tip: On AlmaLinux 10.1, ensure your php.ini has error_log directed to the Apache error log. This ensures that if the "Twin Server" connection drops, the error is recorded by the OS even if Drupal cannot write to its own database. The "Mountain" is now fully transparent. You have the tools to see exactly how your logic flows from the IIS Proxy to the MariaDB core. Would you like me to provide the Composer command to install this "Developer Debugging Suite" so it's ready for your first PoC? AI responses may include mistakes. Learn more