2
hi, thank you for shasring this tool
started to test it, look great, found already parts of my code where I should invest ;)
started to test it, look great, found already parts of my code where I should invest ;)
3
XOOPS 2.7.3 Final Released: PHP 8.6 readiness
The XOOPS Development Team is pleased to announce XOOPS 2.7.3 Final. This release hardens security across the core, prepares XOOPS for PHP 8.6 while remaining fully supported on PHP 8.2 through 8.5, adds SCEditor as an optional BBCode editor, introduces file-based debug configuration with a rotating file logger, and folds in a series of reliability fixes proven in production on xoops.org.
Ready for PHP 8.6
* Complete session save-handler contract: create_sid() ahead of its PHP 9.0 requirement, new sessions survive 8.6's updateTimestamp() routing, session.use_strict_mode pinned to the 8.6 default today
* Deprecations cleared ahead of time: constructor value-returns (guarded by a repository-wide test), is_long(), curl_close(), imagedestroy()
MORE INFO: Read our News Release
DOWNLOAD: You can download the release from here: https://github.com/XOOPS/XoopsCore27/releases
XOOPS 2.7.3 Final Released: PHP 8.6 readiness
The XOOPS Development Team is pleased to announce XOOPS 2.7.3 Final. This release hardens security across the core, prepares XOOPS for PHP 8.6 while remaining fully supported on PHP 8.2 through 8.5, adds SCEditor as an optional BBCode editor, introduces file-based debug configuration with a rotating file logger, and folds in a series of reliability fixes proven in production on xoops.org.
Ready for PHP 8.6
* Complete session save-handler contract: create_sid() ahead of its PHP 9.0 requirement, new sessions survive 8.6's updateTimestamp() routing, session.use_strict_mode pinned to the 8.6 default today
* Deprecations cleared ahead of time: constructor value-returns (guarded by a repository-wide test), is_long(), curl_close(), imagedestroy()
MORE INFO: Read our News Release
DOWNLOAD: You can download the release from here: https://github.com/XOOPS/XoopsCore27/releases
4
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.
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.
5
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 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.
6
XOOPS Plugin for PhpStorm Released
Highlights
* Inspections + Alt+Enter fixes (guards, isResultSet / fetch*, query vs exec, Request, Smarty, templates)
* Live templates, language-constant completion, project scanner tool window
* Module scaffold (legacy or hybrid PSR-4)
* Dynamic plugin where the IDE allows (often no restart after updates)
Early preview — APIs and inspections may change. Feedback welcome via Issues.
DOWNLOAD: You can download the Zip file from here: https://github.com/XOOPS/phpstorm-plugin/releases
MORE INFO: https://xoops.org/modules/publisher/item.php?itemid=6129
XOOPS Plugin for PhpStorm Released
Highlights
* Inspections + Alt+Enter fixes (guards, isResultSet / fetch*, query vs exec, Request, Smarty, templates)
* Live templates, language-constant completion, project scanner tool window
* Module scaffold (legacy or hybrid PSR-4)
* Dynamic plugin where the IDE allows (often no restart after updates)
Early preview — APIs and inspections may change. Feedback welcome via Issues.
DOWNLOAD: You can download the Zip file from here: https://github.com/XOOPS/phpstorm-plugin/releases
MORE INFO: https://xoops.org/modules/publisher/item.php?itemid=6129
7
XOOPS 2.7.3 RC-1 is here — and it brings a new editor.
The first release candidate for XOOPS 2.7.3 is out. Thirty-six changes since Beta 1, and three of them you will notice the day you install it.
A new editor, and one that finally looks the same everywhere
SCEditor joins the editor dropdown as a lightweight BBCode option. It ships bundled, so there is nothing extra to download.
It stays in source mode on purpose, and that is a feature rather than a limitation: a WYSIWYG round-trip is exactly how [siteurl], [d], named [size=] values and custom smilie codes quietly get rewritten or dropped. SCEditor inserts at the caret and leaves the rest of your post alone.
While we were in there, we fixed something long-standing: the same editor now shows the same toolbar everywhere. Until now the control panel and the front end disagreed, and front-end themes disagreed with each other. The cause was five separate hand-written copies of the same markup. There is now one, and every renderer uses it.
Requirements: PHP 8.2+.
More info: https://xoops.org/modules/publisher/item.php?itemid=6128
Download
XOOPS 2.7.3 RC-1: https://github.com/XOOPS/XoopsCore27/releases/
XOOPS 2.7.3 RC-1 is here — and it brings a new editor.
The first release candidate for XOOPS 2.7.3 is out. Thirty-six changes since Beta 1, and three of them you will notice the day you install it.
A new editor, and one that finally looks the same everywhere
SCEditor joins the editor dropdown as a lightweight BBCode option. It ships bundled, so there is nothing extra to download.
It stays in source mode on purpose, and that is a feature rather than a limitation: a WYSIWYG round-trip is exactly how [siteurl], [d], named [size=] values and custom smilie codes quietly get rewritten or dropped. SCEditor inserts at the caret and leaves the rest of your post alone.
While we were in there, we fixed something long-standing: the same editor now shows the same toolbar everywhere. Until now the control panel and the front end disagreed, and front-end themes disagreed with each other. The cause was five separate hand-written copies of the same markup. There is now one, and every renderer uses it.
Requirements: PHP 8.2+.
More info: https://xoops.org/modules/publisher/item.php?itemid=6128
Download
XOOPS 2.7.3 RC-1: https://github.com/XOOPS/XoopsCore27/releases/
8
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 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/
9
Whoops error pages, now only when your site says so.
xWhoops takes PHP's handlers only when XOOPS 2.7.3 has declared it the error-screen owner — not whenever it happens to load. It claims the screen at install, releases it at uninstall, and reports what it did in every branch, including the ones where it declines.
Fixes a long-standing annoyance: Whoops was quietly taking PHP's error handler too, so one harmless notice during boot could replace the page you asked for. It now takes only the exception and shutdown handlers, exactly as the documentation always claimed.
Shows only to an authenticated administrator with the use_xwhoops permission. For development, not production.
Prefer Tracy? xTracy does the same job.
Requirements: XOOPS 2.7.0+ and PHP 8.2+. First beta; feedback welcome.
Download
xWhoops: https://github.com/XoopsModules27x/xwhoops/releases/
Whoops error pages, now only when your site says so.
xWhoops takes PHP's handlers only when XOOPS 2.7.3 has declared it the error-screen owner — not whenever it happens to load. It claims the screen at install, releases it at uninstall, and reports what it did in every branch, including the ones where it declines.
Fixes a long-standing annoyance: Whoops was quietly taking PHP's error handler too, so one harmless notice during boot could replace the page you asked for. It now takes only the exception and shutdown handlers, exactly as the documentation always claimed.
Shows only to an authenticated administrator with the use_xwhoops permission. For development, not production.
Prefer Tracy? xTracy does the same job.
Requirements: XOOPS 2.7.0+ and PHP 8.2+. First beta; feedback welcome.
Download
xWhoops: https://github.com/XoopsModules27x/xwhoops/releases/
10
A Tracy error screen for XOOPS — new module.
xTracy renders uncaught errors through Tracy for developers who prefer it to Whoops. It is a full provider for the XOOPS 2.7.3 error-screen seam: it answers only when the site has named it the owner, refuses for anyone who is not a developer, and reports its outcome to core whether or not it registers.
It exists alongside xWhoops on purpose. Two independent implementations keep the seam an honest contract rather than one module's implementation detail — and they give you a real choice.
Requirements: XOOPS 2.7.0+ and PHP 8.2+. First beta; feedback welcome.
Download
xTracy: https://github.com/XoopsModules27x/xtracy/releases/
A Tracy error screen for XOOPS — new module.
xTracy renders uncaught errors through Tracy for developers who prefer it to Whoops. It is a full provider for the XOOPS 2.7.3 error-screen seam: it answers only when the site has named it the owner, refuses for anyone who is not a developer, and reports its outcome to core whether or not it registers.
It exists alongside xWhoops on purpose. Two independent implementations keep the seam an honest contract rather than one module's implementation detail — and they give you a real choice.
Requirements: XOOPS 2.7.0+ and PHP 8.2+. First beta; feedback welcome.
Download
xTracy: https://github.com/XoopsModules27x/xtracy/releases/
Login
Search
Recent Posts
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Sep 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|