What PHP Debug Information Can You See in the bcons Console?

Updated

bcons shows PHP errors and warnings with source file, line number, and stack trace; log messages and variable values from points you set in code; and session data, cookies, and request payload — all organized into separate tabs with time, domain, source file, and trace data. This applies to any PHP codebase where you can send the bcons HTTP header to enable message forwarding, and you view results either through the browser devtools extension or on the bcons website.

Errors and warnings with full context

Any warning or error your code produces is reported to the bcons console. Each report includes:

  • Source file name
  • Line number
  • Stack trace

That means you don't have to reconstruct where a problem originated from a bare message. The trace data is attached to the message itself.

Log messages and variable values

bcons is described as a companion for debugging tasks such as logging messages or tracking the values of variables at set points in your code. So beyond automatic error capture, you can insert logging calls and inspect what a variable holds at a specific moment — the same role error_log() plays, but surfaced in the browser instead of a server log.

Session data, cookies, and payload

The console also displays:

  • Session data
  • Cookies
  • Payload information

The site's own example illustrates this. A raw FastCGI stderr log shows a checkout request for order sd34s8hd, with the payload action=orderCheckout, orderId=sd34s8hd, session userId=23, and cookies PHPSESSID and userLanguage. In bcons, those same messages appear in separate tabs rather than as one dense log line.

How messages are organized

Each message carries metadata: time, domain, source file, and trace data. Messages are split across separate tabs, which is what makes the volume in the example above readable — payload, session, and cookies each get their own place instead of being interleaved.

Two interaction details from the site: all consoles shown on the bcons page are live, and Ctrl+click on any message element copies it to the clipboard.

How the data gets there

bcons sends an HTTP header that instructs the PHP code to enable sending error and debugging messages to the bcons console. The console itself is available as a browser devtools extension or on the bcons website.

What this replaces

The comparison the site draws is against error_log() and cryptic server logs. The example above is exactly that: a multi-line FastCGI stderr dump where the useful values are buried in PHP message: prefixes. bcons keeps the same information but separates it by type and attaches source and trace metadata.

Practical notes

  • The site lists a three-step setup for the PHP debugger, but the excerpt only shows step 1, so the full sequence isn't reproduced here.
  • Pricing and contact pages exist in the site navigation; no pricing details are given in the available material, so don't assume it's free.
  • The live consoles on the bcons page are demos — clicking around them is a reasonable way to see the tab layout and message metadata before wiring it into your own project.