Blog Sections Open

bDebug: A Lightweight Debugging Tool for Evolution CMS Projects

An ecosystem note on a small debugging helper that made day-to-day Evo troubleshooting much easier.

Debugging tools do not need to be large to be useful. bDebug mattered because it gave Evolution CMS developers a quick, low-friction way to inspect values and understand what the application was really doing during a request.

Simple usage

bLog('$_SESSION', $_SESSION);
bLog('Catalog Test', 'Test test test');

That sort of lightweight logging is exactly what helps when you need to inspect live state without building a larger profiling workflow first.

Historically, tools like bDebug are a reminder that good developer ergonomics in Evo often came from small focused utilities, not only from large modules.

Source: Extras.Evolution catalog entry for bDebug.

Newer post

Rethinking menuindex Increments for Large Evolution CMS Trees

Why larger menuindex steps such as +5 or +10 can make manager reordering easier on large Evolution CMS trees.

Older post

Choosing an E-commerce Module for MODX Evolution

How to think through the choice of e-commerce tooling for MODX Evolution when integration needs, 1C sync, and catalog scale all affect the right answer.