The Diagnostics page now tells you the truth about your error screen..

The error-screen row used to answer "is Tracy installed?" — so a site running xWhoops was told "Not installed" while Whoops was holding the handlers. It now reads what XOOPS 2.7.3 publishes: who owns the screen, where that ownership came from, and whether anything needs looking at. Two modules fighting over it, or one claiming it and quietly failing, is now visible instead of silent.

Also fixes a false "handler drift" warning that appeared on every healthy install, and a toolbar toggle that could erase your recorded error-screen owner.

Requirements: XOOPS 2.7.0+ and PHP 8.2+. First beta; feedback welcome.

Download

Debugbar: https://github.com/XoopsModules27x/debugbar/releases/

The XOOPS DebugBar module is a comprehensive diagnostics and performance toolkit designed for the XOOPS CMS 2.7+ ecosystem. It functions as a "fail-closed" utility, ensuring that diagnostic output is restricted to authenticated administrators and that optional integrations are capability-detected without breaking the core functionality.

Recent updates, specifically versions 1.4.0 and 1.4.1, have transitioned the module from a simple request inspector into a robust developer toolkit. Key advancements include call-site attribution for SQL queries, a granular performance breakdown (Boot/SQL/App time), and real-user monitoring of Web Vitals. Security has been significantly hardened through server-side stashing of SQL for EXPLAIN actions and rigorous literal redaction. The module aims to provide transparency into the XOOPS runtime, identifying bottlenecks such as N+1 query patterns, uncached blocks, and asset duplication.

The XOOPS DebugBar has matured into a comprehensive diagnostics suite that respects both developer efficiency and system security. By naming the "interesting caller," clarifying error-handler ownership, and providing real-user performance metrics, it removes the guesswork from modern web development.