Release history for Override Checker. For install and usage instructions see the documentation.
π Override Checker β Changelog
v2.6.1 2026-11-05
Language-string fix release, plus a check that tells you when an update didn't install completely, and the fix that makes 2.6.0's OpenAI and Gemini scans actually run. Thanks to Scott Forsgren (betterhealthguy.com) for reporting that some strings weren't showing properly. No schema change — safe in-place upgrade from 2.6.0.
New
- The Setup guide recommends the MCP for Override Checker add-on. The MCP card used an old name and offered nothing specific. It now points to MCP for J and its free add-on, which lets an assistant review and fix overrides through tools, with no copy-paste step and no browser timeout.
- Installation file check on the Dashboard. Each of the three extensions in the package now ships an
integrity.jsonlisting the size and SHA-256 of every file it installs. The Dashboard compares them with the disk and shows a red "Installation incomplete" alert naming any file that is missing or 0 bytes, or a yellow alert when files differ from the released version. Joomla does not roll back a failed update, so a half-copied install otherwise keeps running with no warning; security software such as Imunify360 Proactive Defense has been seen killing a copy mid-update and leaving a file at 0 bytes. When everything matches, nothing is shown. This is the Cybersalt standard check from Joomla-Braintools/integrity, translated into all 15 locales. It protects updates from 2.6.1 onward; a failed update to 2.6.1 can't be caught, because the old Dashboard has no check.
Security
- Pre-release security review: whole component, deep pass. No record of a review exists for 2.4.0 through 2.5.0, so this release reviewed every file in the package rather than only the 2.6.1 changes. Findings and what was done are below.
- A fix can no longer add code that runs commands or takes input from a request. Apply-fix writes what the AI sends, and that AI reads site content that could carry a prompt injection asking for a backdoor. Override Checker now compares the new file with the old one and refuses contents that add
eval, shell commands, decoding functions such asbase64_decode, reading or writing files, outbound connections, a new or changedincludeorrequire, variable function calls, or superglobals such as$_GET. Code the file already had can stay, so an override that already contains one of these can still be fixed. It applies to the REST API, the session chat and the MCP for Override Checker add-on, none of which can turn it off. A refused fix writes nothing, returns HTTP 422 (CONTENTS_REFUSED) on REST and is logged asfix_refused. If a change is really wanted, review it and make it in the file yourself. Restore follows the same rule for AI and API callers. Fixing an infected override stores the backdoor as its pre-fix backup, so a restore could have put it back. A restore through REST or MCP that would add such code is now refused (CONTENTS_REFUSED, logged asrestore_refused). A person can still restore any backup from the File backups screen. The check reads PHP only, and enough indirection can get past any list, so keep reviewing what your AI proposes. - Override paths are now validated before any file is read or written. The file path for an override comes from the
hash_idcolumn of Joomla's#__template_overridestable. Nothing checked it for.., and the write allow-list compared the unresolved path text, so a crafted row could point the override-file / core-file endpoints (view permission) at any file on the site, includingconfiguration.php, and point apply-fix and backups at files outsidetemplates/<template>/html/. Planting such a row needs database access or Joomla's own template manager; this extension's API cannot create rows (verified). Paths containing..,., backslashes or NUL bytes, or template names that are not a single folder name, are now refused, and the write allow-list checks the resolved path. Verified on a test site: the crafted read now returns PATH_UNRESOLVED, a crafted write and a symlink escape are both refused, and genuine apply-fix, backup and restore still work. - The REST API no longer has inherited create, edit and delete routes. Joomla's
createCRUDRoutes()also registeredPOST/PATCH/DELETEon/overrides, andDELETEon/sessionsand/backups. They reached Joomla's default handlers and only failed (HTTP 500) because no matching model class exists. They now answer 405 Method Not Allowed explicitly.
Fixes
- Automated scans with OpenAI or Gemini didn't run. 2.6.0 added the AI provider selector, but Run automated scan still checked for an Anthropic key: on a site with only an OpenAI or Gemini key it refused with "No API key is saved", even though the Dashboard offered the button. With an Anthropic key also saved, it sent the Claude model name to OpenAI or Gemini. The scan now checks the selected provider's key and uses that provider's own model setting. The Diagnostics Run test button had the same Anthropic-only key check, and so did the Setup guide's "Method 2 available" badge and the Support page's diagnostics block; all now follow the selected provider.
- Admin text no longer assumes your AI is Claude. About 30 strings written before 2.6.0 still said Claude or Anthropic where any AI applies. Method 2, the confirm and progress messages, and Diagnostics now name the provider you picked ("using your saved OpenAI API key"). The first-run Before you start notice, the Sessions, Backups and Action log descriptions, the paste-a-report form and the "use the manual claude.ai / Claude Code workflow" hints now talk about your AI assistant and the copy-paste prompt. The scan-model help no longer describes Claude models under the OpenAI and Gemini lists, and the Anthropic price estimate and rate-limit tier note show only when Anthropic is selected. The follow-up chat still says Claude, because that chat runs on Anthropic only. All 15 locales.
- The 14 translations had fallen behind the English. 2.6.0 rewrote 20 English strings and the translations were never updated, so every language except English still showed the old Claude-only Dashboard walkthrough ("Method 1: Use Claude.ai or Code"), the old About and sessions text, and the model list as Sonnet 4.6 and Opus 4.7 with old prices, although those options run Sonnet 5 and Opus 4.8. All 20 are now translated from the current English in all 14 locales.
- The "Fetch my Joomla API token" button showed raw language keys. Four of its messages were added in 2.6.0 without language strings, so Options showed COM_CSOVERRIDECHECKER_FETCH_TOKEN_WORKING, …_OFFER_ENABLE (the label of the one-click Enable button), …_OFFER_ENABLE_AUTH and …_SAVE_REMINDER instead of text. All four now have strings in all 15 locales. Reported by Scott Forsgren (#2).
- The same button's "plugin disabled" warnings showed HTML tags as text. The messages wrap the plugin name in
<strong>, but the note was written withtextContent, so it read "The <strong>User - Joomla API Token</strong> plugin is disabled…". The note now renders<strong>as bold and still treats everything else as plain text, so an error message coming back from the server cannot inject markup. - The admin sidebar showed raw keys for two Override Checker menu items on every page outside the component. The Setup guide and Get help entries added in 2.6.0 used
COM_CSOVERRIDECHECKER_TOOLBAR_SETUPGUIDEand…_TOOLBAR_SUPPORT, which were only in the component's.ini. Joomla loads only the.sys.inifor the menu outside the component, so on the Home Dashboard, Plugins, Scheduled Tasks and every other screen they read as raw keys. Both keys are now in the.sys.iniof all 15 locales; existing menu entries pick them up without a menu rebuild. - The Options page heading and browser tab showed
com_csoverridechecker_configuration. Joomla's Options screen looks upCOM_CSOVERRIDECHECKER_CONFIGURATION, which the component never defined. It now reads "Override Checker: Options", matching core ("Articles: Options"), in all 15 locales. - Browser tab title showed a raw HTML entity on the Setup guide and Get help pages.
ToolbarHelper::title()escapes its argument, so the—in those two title strings rendered literally. Both now use a real em dash. Fixed in all 15 locales. - Anthropic key note still named the wrong default model. It read "defaults to Claude Opus 4.7" after the default moved to Opus 4.8. Fixed in all 15 locales.
v2.6.0 2026-08-29
Assistant-agnostic release. The extension has always been drivable by any AI that can make an HTTPS request, but the admin interface read as though Claude were a requirement. This release fixes that in the product itself, and adds the built-in support area the Cybersalt extension standard calls for.
New Features
- Setup guide view. Answers "which AI can I use?" from inside the admin. Leads with the actual capability an assistant needs — outbound HTTPS with a custom header, plus POST with a JSON body to apply fixes — rather than a product list that goes stale. Per-family notes for terminal and editor agents, browser chat assistants, custom GPTs and Gems, local and self-hosted models, and MCP clients, plus the endpoint URL and
X-Joomla-Tokenauth warning. - Support area. States plainly that the extension is free with no Pro tier, sets honest expectations about free-support response times, points at GitHub Issues, lists what to include in a report, and renders a copyable diagnostics block (extension / Joomla / PHP versions, site URL, key and token presence). The block contains no secrets — only presence flags, never values — so it is safe to paste into a public issue.
- Both views are reachable from the dashboard button row, the toolbar, and the component submenu.
Improvements
- Dashboard copy is no longer Claude-specific. "Method 1: Use Claude.ai or Code" becomes "Method 1: Use your AI assistant", and the step-by-step instructions, continue-a-previous-review card, sessions blurb and About description were rewritten to describe the workflow without naming a vendor.
- The one vendor-locked path is labelled as such. Method 2 calls Anthropic's API directly and cannot use another provider's key. The Setup guide says so outright and points users at Method 1 instead.
No schema change — safe in-place upgrade from 2.5.1. New strings are en-GB only in this release; the other 14 locales fall back to English for the two new views until the translation pass lands.
v2.6.0 2026-08-29
Copy-accuracy and documentation release. Two user-visible strings were stating things that stopped being true in v2.4.3, and the permissions screen was leaking an internal identifier at end users. Both fixed in all 15 languages. No functional or schema change — safe in-place upgrade from 2.5.0.
Bug Fixes
- Permissions screen no longer shows the raw element id. The two custom ACL actions rendered as "View csoverridechecker data" and "Modify csoverridechecker data and override files" in Options → Permissions, exposing the internal element name to site administrators. They now read "View Override Checker data" and "Modify Override Checker data and override files". Fixed in all 15 locales (30 strings), preserving each existing translation.
- Options help text corrected.
COM_CSOVERRIDECHECKER_CONFIG_ANTHROPIC_API_KEY_NOTEstill claimed the default model was Claude Sonnet 4.6 and that scans were "capped to the first 60 per run". Both changed in v2.4.3 — Opus 4.7 is the default and the cap default is 10. Fixed in all 15 locales.
Documentation
- Full end-user documentation published at docs.cybersalt.com/extensions/override-checker — install, all three review workflows, reading a report, applying and rolling back fixes, the audit trail, permissions, the Web Services API reference, troubleshooting, FAQ and support. Illustrated with 15 lossless-WebP screenshots.
- Documentation is now assistant-agnostic. The REST API has always been open to any AI that can make an HTTPS request, but the docs read as though Claude were required. They now lead with a three-method chooser, document the capability an assistant needs rather than naming products, and carry per-assistant notes for terminal agents, browser chats, Custom GPTs, local models and MCP clients. The built-in automated scan now offers Anthropic, OpenAI or Gemini; the one genuinely vendor-locked path — the follow-up chat that applies fixes — is labelled as such.
- Documentation updated for this release. Method 2 rewritten for the three-provider selector; new sections covering the Setup guide and Get help views; the Joomla API token section rewritten around the one-click Fetch my token button and the two plugins a token depends on; hold-to-reveal secret blurring documented; troubleshooting gained rows for the silent
401caused by a disabledplg_api-authentication_tokenand for the chat box being absent on non-Anthropic providers. Five screenshots reshot from the live 2.6.0 admin and two added.
v2.5.0 2026-06-26
Internal rename release. v2.4.4 fixed the user-visible name but every internal identifier (element id, namespace, table prefix, file paths) still referenced "templateintegrity". This release renames all of them and ships a one-shot migration script so existing v2.4.x installs upgrade cleanly without losing data.
Improvements
- Internal identifier rename:
cstemplateintegrity→csoverridecheckereverywhere. Element ids (pkg_csoverridechecker,com_csoverridechecker,plg_webservices_csoverridechecker,plg_task_csoverridechecker), PHP namespaces (Cybersalt\Component\Csoverridechecker\β¦), database tables (#__csoverridechecker_*), language keys (COM_CSOVERRIDECHECKER_*etc.), scheduler task type (csoverridechecker.purgeBackups), Web Services API route (/api/index.php/v1/csoverridechecker/overrides), file and folder names — all aligned with the public display name. 168 files modified, 99 files renamed, 6 directories renamed. - Web Services API URL changed. Overrides endpoint moves from
/api/index.php/v1/cstemplateintegrity/overridesto/api/index.php/v1/csoverridechecker/overrides. Any Claude / MCP client configured against the old URL will need to be reconfigured. There is no compat alias.
Migration (automatic)
The pkg_csoverridechecker installer detects an existing pkg_cstemplateintegrity install and runs a one-shot migration before showing the postinstall card:
- Copies extension params (API key, scan model, chat model, cost caps, etc.) from old component, webservices plugin, and task plugin to their new counterparts.
- Copies all rows from
#__cstemplateintegrity_sessions,_actions, and_backupsinto the new#__csoverridechecker_*tables. - Rewrites
#__scheduler_tasksrows wheretype='cstemplateintegrity.purgeBackups'to the new task type, so the user's existing schedule continues to run on the new plugin. - Renders a one-time card on the install page explaining the rename and offering a one-click button to the Extensions Manager filtered for the legacy package, ready to be uninstalled.
Idempotent: only runs on first install of pkg_csoverridechecker (not subsequent updates), only runs if the legacy extension is present, aborts if the new tables already contain data. After migration the legacy pkg_cstemplateintegrity package remains installed but inert until the user uninstalls it explicitly.
Notes for users
- Old package's update feed is frozen at v2.4.4. Existing sites with the old package installed will not see v2.5.0 in their normal Joomla update list — there is no upgrade path from
pkg_cstemplateintegritytopkg_csoverridecheckerthrough the update feed. Installpkg_csoverridechecker_v2.5.0.zipfrom the Joomla Extension Directory listing or the GitHub release; the migration runs automatically. - Reconfigure any external clients. If you have Claude (or any other API consumer) configured against
/api/index.php/v1/cstemplateintegrity/overrides, update it to/api/index.php/v1/csoverridechecker/overrides.
v2.4.4 2026-06-24
JED-submission release. Two fixes spotted by JED Checker on the v2.4.3 package, both prep for the formal Joomla Extension Directory listing.
Fixes
- Build script: package zip now ships every locale's
pkg_*.sys.ini. The<languages>block in the package manifest declares all 15 locales butbuild-package.ps1was only copyingen-GB's package-level sys.ini into the staging root before zipping — Joomla's installer never complained (it falls back to en-GB) but JED Checker flagged 14 "File not found" entries. Build script now does a singleCopy-Item -Recurseof the entirelanguage/tree so every locale's sys.ini ends up in the zip.
Improvements
- Extension renamed: "Cybersalt Template Integrity" → "Cybersalt Override Checker". JED's naming policy bars the reserved word Template in extension names (alongside Module, Plugin, Component, etc.). Override Checker is more precise about what the extension actually monitors (template overrides) and keeps the brand half of the name. Cosmetic only: every internal identifier stays the same —
pkg_cstemplateintegrity,com_cstemplateintegrity,plg_webservices_cstemplateintegrity,plg_task_cstemplateintegrity, theCybersalt\Component\Cstemplateintegrity\β¦PHP namespaces, the#__cstemplateintegrity_*database tables, the GitHub repocs-template-integrity, and the update-server URL (element=pkg_cstemplateintegrity) all remain untouched. Existing installs upgrade in place with no migration. 387 substring replacements across 102 files.
Migration
In-place upgrade from 2.4.3. No schema changes; no settings changes; no data migration. The first time the admin opens the component after the upgrade, they'll see "Override Checker" in the Components menu where "Template Integrity" used to be. Nothing else changes.
v2.4.3 2026-06-22
Auto-scan UX + Opus-as-default release. The automated scan report now produces the same copy-paste-able "Suggested next-turn prompts" the manual workflow has had since v2.3.4 — three prompts when the batch covered everything, four when more overrides remain. The chat agent no longer requires a typed "confirm" when the user's instruction already names explicit numbered finding ids. Opus becomes the default model for both scan and chat. Cross-locale parity sweep brings 14 other languages in line with the en-GB Options-tab labels and copy.
New
- Auto-scan report now includes "Suggested next-turn prompts" (section f). Mirrors the manual workflow's v2.3.4 format: a short heading per prompt, the exact text the user pastes back into the session chat box, with real finding ids substituted (never placeholders). When the scan was capped at
scan_max_overridesand more flagged overrides remain in the tracker, a fourth prompt appears at the top — Continue with the next batch of overrides — and the second and third prompts pick up a "β¦then check the next batch" tail. When the batch covered everything, the standard three-prompt format is used unchanged from the manual workflow. - Auto-scan system prompt explicitly forbids "contact a developer" advice. v2.4.2 reports occasionally suggested users hire a developer to make changes — even though the user has Claude available right there in the session's chat box with the apply_fix / dismiss_override tools. The new system prompt directs Claude to point users at the section (f) suggested prompts instead.
Improvements
- Opus 4.7 is now the default model for both Scan model and Chat model in Options. Applied consistently across
config.xml, every PHP fallback path, and the localised model option labels / descriptions. Opus is the most thorough classifier and the most reliable tool-use model — the safer default for a security review extension. Cost goes up ~5× per scan vs Sonnet; the Cost difference note in Options has been rewritten to explain this and frame the numbers with "At the time of writing thisβ¦" so users know to verify against current Anthropic pricing. - Chat agent — no more "type 'confirm' to proceed" interruption. When the user's instruction names explicit numbered finding ids (one or many), the chat agent now proceeds directly with the apply_fix / dismiss_override calls. The ids ARE the confirmation;
apply_fixstill auto-backs-up to#__cstemplateintegrity_backupsbefore writing, so any individual patch is reversible from File backups regardless. The anti-ambiguous-pronoun guard from v2.3.4 is preserved — "fix those" / "mark them all checked" without ids still triggers a stop-and-ask. - Cross-locale "AI provider" → "Keys & tokens" parity sweep. Three help / error strings in every locale (
AUTOSCAN_NOTE,RUN_SCAN_NO_KEY,SESSION_CHAT_NOKEY) referenced the Options tab by its old internal name AI provider. The actual tab label has been Keys & tokens in every locale since v2.4.2; this release brings the help strings in line. 44 substring replacements across 15 locale files. - Cross-locale Opus-as-default translations. The five model-related Options strings (
SCAN_MODEL_DESC,CHAT_MODEL_DESC,MODEL_SONNET,MODEL_OPUS,MODEL_COST_WARNING) re-translated in all 14 non-en-GB locales to reflect the new Opus default and the "At the time of writing this" cost framing. 70 substring replacements.
Migration
In-place upgrade from 2.4.2. No schema changes; no settings changes. Existing sites that had claude-sonnet-4-6 saved explicitly in Options will keep using Sonnet — the default only applies to new installs or sites that never set the value. Admin users who want Opus on an existing site should open Options → Keys & tokens and pick Opus 4.7 in the Scan model and Chat model dropdowns.
v2.4.2 2026-06-12
UX polish release: clearer first-run guidance about saving API tokens in Options, a more readable "Before you start" disclaimer modal on light-mode admins running dark-mode OSes, and a shorter Components-menu label. PHP minimum bumped to 8.3 in line with the new Cybersalt extension baseline.
Improvements
- Components menu label shortened to "Override Checker" (from "Cybersalt Override Checker"). Applied to all 15 locale INI / SYS.INI files. The extension's full name and branding are unchanged everywhere else.
- Method 1 (manual) — Step 1 copy rewritten. Step 1 now explains that the Joomla API token can be saved into the component's Options → Keys & tokens tab, and the dashboard prompt will then auto-fill with it on every scan. Users who'd rather not save the token still see the same single-paste instruction.
- Method 1 — Step 2 placeholder-replace is now conditional. Step 2 tells users to replace the
<PASTE YOUR JOOMLA API TOKEN HERE>placeholder only if they did not save the token in Step 1. A new paragraph recommends Claude Code over the browser, because at lower Claude plan tiers the review can take long enough that claude.ai in a browser hits its request timeout before Claude finishes responding. - Method 2 (automated) — no-key copy now points at the Options button on the card (was "in the toolbar above"), names the correct fieldset (Keys & tokens, not AI provider), and explicitly reassures users that the key stays in their own site's database.
- All 14 non-en-GB locales updated to match the en-GB rewrites.
Fixes
- Disclaimer modal contrast on light-mode admins with dark-mode OSes. v2.4.1's modal CSS honoured
prefers-color-scheme: dark, which flipped the popup to dark even when the Joomla admin behind it was rendering light — and the host's light-mode--bs-link-color(a dark navy) bled into the dark popup, rendering "Don't show this again" unreadable. v2.4.2 removes the OS-preference branch entirely (popup now tracks only the admin template'sdata-bs-theme/data-color-schemeattribute), scopes--bs-link-colorinto the card so host values can't leak, and forces<p> <label> <li>inside the card tocolor: inherit !importantdefeating any host-template label-as-link styling. - Disclaimer modal — "Don't show this again" row now visibly clickable. The row's background and border opacities were so subtle (4% / 8% in light mode) that users missed it was a checkbox. Bumped to 6% / 20% in light mode and 8% / 25% in dark mode.
Maintenance
- PHP minimum bumped from 8.1 to 8.3 in
updates.xml. Reflects the new Cybersalt-wide baseline for all our Joomla extensions.
Migration
In-place upgrade from 2.4.1. No schema changes; no settings changes. The disclaimer modal will re-render with the readable styling on the next page load; the Components menu label will refresh on the next Joomla admin session.
v2.4.1 2026-06-12
Maintenance release: switches the Joomla update channel from raw.githubusercontent.com to the Cybersalt Release Manager on cybersalt.com. No code or feature changes.
Improvements
- Update server moved to the Cybersalt Release Manager. The
<updateservers>URL in the package manifest now points at the Cybersalt Release Manager'sapi.updatexmlendpoint (withelement=pkg_cstemplateintegrity) instead of the staticupdates.xmlon GitHub raw. Existing v2.4.0 sites discover this release through the old GitHub channel one last time; from v2.4.1 onwards they check the Cybersalt endpoint directly. SHA256 verification by Joomla's updater is unchanged.
Migration
In-place upgrade from 2.4.0. No schema changes; no settings changes. After this update is installed, the new update-server URL is registered on the site and all future update checks go through cybersalt.com.
v2.4.0 2026-05-25
Feature release: scheduled-task plugin for purging old file backups, so the #__cstemplateintegrity_backups table doesn't grow indefinitely. Backup rows are intended as a short-window safety net for restoring a file after a Claude-applied patch; without a retention policy they accumulated forever.
New
- New plugin:
plg_task_cstemplateintegrity(grouptask). Registers one Scheduled-Tasks routine: "cs-template-integrity: Purge old file backups". Auto-enabled on install. Three per-task parameters:- Retention window (days) — default 30. Rows older than this are eligible for deletion.
- Always keep this many most-recent backups — default 5. Safety floor: even if all rows are older than the retention window, the N most-recent are never deleted, so the user always has a usable roll-back window.
- Dry run — default Off. When On, the task counts what would be deleted and writes the count to the Action log, but makes no DB changes. Use this to verify a new config before letting it run for real.
- Default scheduled task seeded on install with retention 30 / min_keep 5 / dry_run Off / interval 24h / state unpublished. The admin reviews and enables it under System → Scheduled Tasks. Seeded unpublished so the very first daily tick doesn't delete pre-existing backups before the admin has reviewed the config. Idempotent — re-installs don't create duplicates.
ACTION_BACKUP_PURGEDentries now appear in the Action log on every task run, with the full result struct (deleted, would_delete, kept_by_floor, retention_days, min_keep, cutoff, dry_run). Visible in the existing filterable Action log list view.
Improvements
- Package installer auto-enables both child plugins (the existing
webservicesplugin and the newtaskplugin) — Joomla installs third-party plugins disabled by default, so without this the API routes 404 and the task type doesn't appear in the Scheduled-Tasks dropdown until the admin manually flips them on. - Language shim for
COM_SCHEDULER_PARAMETERS_FIELDSET_LABEL— Joomla 5.x en-GB packs on some point releases are missing this core key, so the "Parameters" tab on the task edit screen rendered as the raw key string. The plugin's language file now defines the key so the global string pool resolves it on every install.
Migration
In-place upgrade from 2.3.5. Schema-compatible. The default purge task is seeded once; on update from 2.3.5 a single seed runs (skipped on subsequent updates via the existing-task idempotency check).
v2.3.5 2026-05-25
Prompt-only patch release: closes a false-negative footgun in the scan-with-Claude review pass.
Security
- Scan prompt now forbids assumption / inference shortcuts during the review pass. A real test run flagged only 1 critical security finding on a site that had 2 — when investigated, Claude reported that it had "assumed something when searching" rather than fetching and reading every file independently. The model had cleared a file because it looked similar to an already-cleared neighbour. The scan prompt now includes a non-negotiable "No-assumptions rule": every flagged override must be fetched before any verdict is issued, and inference from filename / path / template / similar-looking-files-already-cleared is explicitly forbidden. Files that were not actually fetched (e.g. because of an API budget cap) cannot get a verdict — they must be listed as "not examined this run" with a βΈοΈ icon.
- Findings-table completeness audit added to step 4. Before publishing the report, the model must verify that the table contains a row for every flagged id returned by
GET .../overrides. Silent omissions read as "clear" and produce exactly the kind of false negative this release fixes; the audit catches the omission before the report goes out. A new βΈοΈ severity icon distinguishes "not examined this run" from clean βͺ INFO so the gap is visible to the user.
Migration
In-place upgrade from 2.3.4. No schema changes; no settings changes. Existing sessions continue to use whatever prompt was in effect when their scan ran — re-run the scan to get a report under the new rules.
v2.3.4 2026-05-21
Prompt-only patch release: closes the "act on ambiguous pronouns" footgun that has bitten test sessions since chat-with-Claude landed.
Security
- Scan prompt now produces "Suggested next-turn prompts". Every Claude-generated scan report ends with three copy-paste-able prompts the user can send back to drive the next chat turn. Each prompt names finding ids explicitly (e.g.
Fix #1, #3. Mark #2, #4, #5 as checked.) instead of pronouns like "mark these" or "fix the critical ones". Reason: in real test sessions the chat agent has misread "mark these as checked" (referring to a small subset) as "clear every row in the tracker" — wiping 70 rows on one occasion. With explicit numbered ids the user retains precision and the model has no ambiguous pronoun to resolve. - Chat system prompt now refuses ambiguous-pronoun instructions. The chat agent must STOP and ask which specific finding numbers the user means whenever the instruction uses pronouns or vague references ("them all", "those", "the critical ones") without concrete ids. It must also restate the plan and wait for explicit
confirmbefore any destructive action that touches more than one row. Single-row actions with an explicit id can still proceed immediately. Belt-and-braces alongside the v2.3.3 removal of thedismiss_allchat tool.
Migration
In-place upgrade from 2.3.3. No schema changes; no settings changes. Existing sessions continue to use whatever prompt was in effect when their scan ran — re-run the scan to get a new report with the Suggested next-turn prompts section.
v2.3.3 2026-05-21
Iteration release: chat-with-Claude stability, dashboard polish, and two new list views (Action log + File backups) with sortable headers and a Joomla-native filter bar.
New
- Per-template rescan picker. The dashboard's "Reset overrides for review" button now opens a modal with one checkbox per template that actually has an
html/override directory on disk. Tick which templates to rescan, optionally Select all, submit only when at least one is chosen. The controller validates posted ids against the on-disk whitelist server-side so a hostile post can't reach templates the picker didn't surface. - File backups list — Restore button per row. A new green Restore icon button on each backup row submits to the existing
backups.restoretask (auto-backs-up the live file first, then writes the saved bytes). JSconfirm()shows the destination path before submitting. - Filter bar on Action log + File backups list. Joomla-native
js-stoolsmarkup with Choices.js-wrapped dropdowns: search + action-type / session dropdowns, limit dropdown (20/50/100/200/500), Filter Options collapse, Clear button. Sessions render with#N — namelabels. - Sortable column headers on both list views. Action log sorts by Time / Action / Session; File backups sorts by Saved / File / Size / Session. URL state preserves filter+sort+limit across navigation and back/forward.
- Date + time on both list views.
SavedandTimecolumns stackYYYY-MM-DDon top ofHH:MM:SSin muted text — easier to sort visually within the same minute. - API tier note on the Method 2 card. Explains that Anthropic's default Tier 1 (10,000 input tokens/min) is fine for one-shot scans but rate-limits during multi-turn chat fixes; Tier 2 (50,000 tokens/min, billed) is comfortable. Direct link to
console.anthropic.com/settings/limits. - Dashboard "Open Options" button appears below the no-API-key warning. Goes to the component's Options form with a base64-encoded
return=param pointing back at the dashboard, so once the user saves a key they land back on the dashboard automatically.
Security
- API key field now uses native browser password masking. The
<input>element renders withtype="password"so bytes are masked the instant they're typed or pasted. Previous v2.0–v2.3.2 used a CSSfilter: blur()overlay that briefly showed values during paste and removed the blur on focus. The Reveal toggle now swaps the input type rather than toggling a CSS class. Underlying FormField PHP class is stillTextFieldso values round-trip through Joomla's save path untouched. dismiss_alltool removed from the chat agent. A test session reproduced an unsafe model interpretation: when told to "mark these 10 as checked", Claude invokeddismiss_alland cleared all 70 tracker rows. The chat agent now only exposes per-rowdismiss_override; bulk-clear lives in the dashboard's per-template rescan picker.- Absolute server path removed from override-file / core-file API responses. The
data.attributes.absolutefield leaked the hosting account's filesystem layout (e.g./home/<user>/public_html/...) to anyone holding a valid Joomla API token. Redundant with the already-relativizedpathfield; removed.
Fixes
- Sortable column headers actually sort now. First implementation passed the sort URL through
Route::_()without thexhtml=falseargument, so it returned&-encoded URLs.htmlspecialcharsthen double-encoded to&amp;, the browser decoded that once to&and PHP parsed query keys asamp;view,amp;sort— with no realview=present, Joomla defaulted to the dashboard. Fixed. - Chat-with-Claude no longer 400s on "tool_use ids without tool_result blocks immediately after". The chat loop's
MAX_TURNScap (was 12, now 24) could exit the conversation in an[..., assistant tool_use, user tool_result]state when Claude needed more rounds than the budget allowed. A newrepairToolUseChain()runs both before adding a new user message and before persisting: synthesises "tool execution was interrupted" tool_result blocks for orphan tool_use ids, reorders tool_results to the front of mixed user content, and merges consecutive same-role messages. - Restore-from-list no longer lands on the backup detail page. Previous flow always redirected to
view=backup&id=...after restore, where the page is still titled "Backup #N" and shows the existing "Restore now" modal — looked unfinished. - Empty Anthropic API key field no longer rejected on save. Component config XML allows an empty string so users can clear a saved key without form-validation errors.
Improvements
- Chat-with-Claude rate-limit posture for the 10K TPM tier. Older tool payloads compressed at API-send time (
apply_fixinput bodies andget_override_file/get_core_fileresult contents over 1KB get stripped from old turns and replaced with(N bytes — compressed from history)markers). Per-turn tool-result byte cap: when Claude fan-out-calls many tools in one round, the loop executes tools in order and stops calling once cumulativetool_resultpayload exceeds 12 KB. System prompt steers toward small batches and terse replies. - Dashboard "Run automated scan now" button is now green (
btn-success) instead of blue. Blue stays for copy-the-prompt buttons; green is the action that actually runs something on your site. - v2 review prompt rewrite. Tightens the scan-with-Claude prompt with field-tested corrections: severity now judged relative to core (was absolute, falsely flagged every legacy override that mirrors core's intentionally-raw output), normalize-before-diff rule, alternative-layout handling (no core counterpart), mandatory code-execution indicator scan with a fixed pattern list, JSON:API response shape docs, STOP-on-write-failure rule, privilege precondition required on every ALERT, framework-generated overrides (TCK/Helix/Gantry/YOOtheme) routed to REVIEW not ALERT, token-hygiene paragraph.
Migration
In-place upgrade from 2.3.2. No schema changes; no settings changes. Existing chat sessions stuck in the old shape repair themselves on the next chat turn.
v2.3.2 2026-04-29
Single-purpose patch release: fixes the empty-changelog-modal in Joomla's Extension Manager.
Fixes
- Extension Manager changelog modal now renders correctly. Joomla's
<changelogurl>expects a Joomla-format XML feed (<changelogs>root with versioned<changelog>entries containing<addition>/<fix>/<security>/<language>etc.), not human-readable HTML. From v2.0 onwards the manifest pointed atCHANGELOG.html, so clicking the version badge in Extensions → Manage opened an empty modal for the entire 2.x series. Addedchangelog.xmlat the repo root in the format Joomla actually parses, and switched both the package manifest andupdates.xmlto point at it.CHANGELOG.htmlandCHANGELOG.mdremain as the human-readable pair, linked from the README.
Migration
In-place upgrade from 2.3.1. No schema changes; no settings changes. The fix takes effect on this install — sites running 2.3.1 or earlier continue to see an empty changelog modal until they upgrade to 2.3.2 (the <changelogurl> is baked into manifest_cache at install time).
v2.3.1 2026-04-29
Completes the multilingual rollout started in 2.3.0: all 14 non-English language packs are now fully translated (no more English fallback for any string).
New
- Full translations for all 14 additional languages. Every one of the 246 admin strings — plus the 5 system/API/package/plugin language files in each language — now ships translated.
- Romance: fr-FR (French), es-ES (Spanish), it-IT (Italian), pt-BR (Brazilian Portuguese)
- Germanic / Northern European: nl-NL (Dutch), sv-SE (Swedish)
- Slavic: ru-RU (Russian), pl-PL (Polish), cs-CZ (Czech)
- Other European: tr-TR (Turkish), el-GR (Greek)
- East Asian: ja-JP (Japanese), zh-CN (Simplified Chinese)
- All translations use the formal admin-tool register appropriate to each language. Brand names (Cybersalt Override Checker, Anthropic, Claude, Joomla, Akeeba Backup), technical acronyms (API, REST, XSS, SQL, CSRF, JSON, HTTP, PHP), code references (
#__template_overrides,JPATH_ROOT,sk-ant-β¦, file paths, class names), URLs, and printf placeholders (%s,%d,%1$d) are preserved untranslated per Joomla extension convention.
Improvements
- The Options → Keys & tokens tab and every dashboard string render in the admin's chosen Joomla language out of the box — no further configuration needed.
Migration
In-place upgrade from 2.3.0. No schema changes; no settings changes. Admin users whose Joomla language is set to any of the 14 supported tags will now see the full UI in their language. Native review by a fluent speaker is recommended for the East Asian (ja-JP, zh-CN) and Slavic / Eastern European (cs-CZ, el-GR, tr-TR) translations before depending on them in customer-facing scenarios — open a PR or email
v2.3.0 2026-04-29
Multilingual support: language pack registered for all 15 of Cybersalt's standard languages.
New
- Language packs registered for
en-GB,de-DE,fr-FR,es-ES,it-IT,pt-BR,nl-NL,ru-RU,pl-PL,ja-JP,zh-CN,tr-TR,el-GR,cs-CZ,sv-SE. All 6 language files (admin .ini + .sys.ini, api .ini, package .sys.ini, plugin .ini + .sys.ini) ship in every language. Joomla picks the active language automatically based on the admin user's preference. - German (de-DE) fully translated — every one of the 246 admin strings, plus all 5 system/API/package/plugin language files. Real translations, not machine output. Uses formal “Sie” register appropriate for admin tooling.
- Other 13 languages — language directories registered with English fallback content (so the language pack installs cleanly and Joomla resolves to English wherever a translation isn't yet shipped). Real translations rolling out in 2.3.x patch releases.
Migration
In-place upgrade from 2.2.x. No schema changes; no settings changes. After install, an admin user whose Joomla language is set to de-DE will see Cybersalt Override Checker in German throughout. Other configured languages will continue to display English admin copy until their patch release lands.
v2.2.0 2026-04-29
UX rework on the dashboard: clearer "what do you want to do today" path-finding with two action shortcuts and a Cybersalt orange + Bootstrap blue palette; nicer key/token Options UX with Reveal / Clear / Get-token buttons; brand pass on every user-facing title; full-component security review with eight findings closed.
New
- Method 1 / Method 2 action shortcuts at the top of the dashboard. Method 1: Use Claude.ai or Code (Cybersalt orange) anchor-jumps to the copy-paste prompt below; Method 2: Run automated scan (Bootstrap blue, or grey-outlined when no API key is saved) jumps to the auto-scan card. Two clearly-named paths replace the old "everything's at the bottom" layout.
- Clear button on every API-key / token field in Options → Keys & tokens (the old AI provider tab — renamed). Click to empty the field; save persists. Joomla API token field also sprouts a Get token button that opens the current admin's profile in a new tab; the button auto-hides once a token is entered and reappears the moment the field is cleared.
- Empty-state blur skip on key/token inputs — the input no longer renders blurred when it's empty, so admins can see where to paste on a fresh field.
- Mode-aware Rescan button — solid yellow with dark text in light mode, outline-yellow on near-black in dark mode. Reads as a "warning" intent in both modes without the contrast trap of
btn-outline-warningin light mode.
Improvements
- Dashboard restructure. Removed the API endpoint active status alert, the Recent sessions card (the Sessions menu covers it), and the Mark all as reviewed shortcut (Claude's
dismiss_alltool covers that path). Right-hand About sidebar moved to a full-width footer so the action methods get the full canvas. Section reading order: Method 1 → Continue Previous Review → Method 2. - Cybersalt action-button palette. Method 1 uses
#dc6b1aCybersalt orange with white text; Method 2 (with API key) uses Bootstrap blue. Navigation buttons (Sessions / File backups / Site Templates Management / Action log) are neutral grey — "go fetch data" buttons, not primary actions. - Top nav reordered alphabetically — Action log → File backups → Open Site Templates Management → Sessions → Rescan → Diagnostics. Site Templates Management opens in a new tab.
- Side-menu reorder — Dashboard → Action log → File backups → Sessions inside the component admin sidebar.
- Brand pass. Every user-facing page title now reads Cybersalt Override Checker (was CS Override Checker) — Sessions / Action log / File backups / extension manager / API component label / update server name. Code-side identifiers (namespaces, language string keys, file paths, DB tables) keep the
csshort form. - Get token link lands on the current admin's user-edit form (
view=user&layout=edit&id={current admin}) instead of falling through to the user list. Route URLs are single-encoded (no more double&amp;in the rendered href). - Dark-mode prompt cards are slightly elevated so the card edge reads as a real container instead of blending into the page background. Light mode unchanged.
Security
Eight findings from the v2.0–v2.2 retroactive review closed in this release:
- H-1 — Joomla API token plaintext exposure (privilege escalation). A user with
cstemplateintegrity.viewcould read the higher-privileged admin's saved Joomla API token off the dashboard's prompt block, and then authenticate against the entire Joomla Web Services API as the issuer (full privilege escalation outside cstemplateintegrity's scope). The dashboard view now substitutes the token only when the current user holds the write tier — view-tier users see the<PASTE YOUR JOOMLA API TOKEN HERE>placeholder. - M-1 — Backup restore path-safety hardening. v0.9.0 closed the live RCE primitive but the restore-side guard still permitted writes anywhere under
JPATH_ROOTfor any non-PHP extension —.htaccess,.user.ini, or template.css/.jscould be overwritten via a write-tier user with seeded archival backup rows.PathSafetyHelper::assertOverrideWriteAllowed()is now a positive allow-list: every write must terminate inside<root>/templates/<tpl>/html/or<root>/administrator/templates/<tpl>/html/regardless of file extension. - M-2 — Disk-fill primitive on apply_fix and restore. Neither write path capped the size of the new contents being written. New 4 MB upper cap enforced before
file_put_contents()in both paths. - M-3 — apply_fix silently failed on >1 MB legitimate overrides. Backup row size cap raised from 1 MB to 4 MB so apply_fix can both snapshot and write on real-world large overrides.
- L-1 — Anthropic API key fingerprint narrowed brute-force search. Diagnostics fingerprint previously rendered
starts="<first 8>", ends="<last 4>"of the saved key. Replaced with a 12-char SHA-256 prefix — admins can still verify "this is the key I think it is" but no chars of the actual key leak. - L-2 — Web Services apply-fix accepted nonexistent session_id. Audit-trail integrity bug. The endpoint now validates
session_idreferences an existing session row; non-existent ids return 400INVALID_SESSION_ID. - L-3 — Defense-in-depth on
simplexml_load_file(). Now passesLIBXML_NONETexplicitly — belt-and-braces for older PHP and future libxml default changes. - L-4 — Per-user soft cap on automated scans. Run automated scan now refuses if the current user has logged 12+ scan attempts in the past hour. Defends against accidental click-spam and against a CSRF-coerced admin (or compromised account) burning the saved Anthropic key's spend quota.
- L-5 — Session-download filename consistency. A session named
..or.previously produced cosmetically odd download filenames. Sanitization now strips leading/trailing dots and falls back tosession-<id>when empty.
Docs
- Joomla Brain UI patterns — new section documenting the Cybersalt action-button palette, role/class/color table, "avoid" list, and CSS recipes for the orange Method 1 button and the mode-aware Rescan button. Future Cybersalt extensions can copy-paste from there.
- Joomla Brain company-info — new "
csprefix vs. 'Cybersalt' full name" section so the next extension doesn't drift between the technical short form (in code) and the brand name (in user-facing strings). - Joomla Brain version-bump checklist — security review is now a hard prerequisite before any version bump. Routine bumps use the 0.7 confidence threshold; major bumps drop to 0.5 and require PHPStan in addition.
Migration
In-place upgrade from 2.1.x. No schema changes; no settings changes. Backup-row size cap bump from 1 MB to 4 MB doesn't affect existing rows. Side menu reorder takes effect on next admin cache clear. View-tier users who previously saw the saved Joomla API token in the dashboard's prompt block will now see the placeholder instead — restore the convenience by ensuring those admins also hold cstemplateintegrity.write (or core.manage).
v2.1.0 2026-04-29
New
- Choose your Claude model for the automated workflow. Two new dropdowns under Components → CS Override Checker → Options → AI provider:
- Scan model — for the one-shot Run automated scan. Default Sonnet 4.6. Haiku cuts cost ~3× with no real quality loss on classification; Opus is overkill for routine scans but useful for security-sensitive sites.
- Chat model — for the tool-use loop. Default Sonnet 4.6 — tool use is harder than classification, so even if you go Haiku for scan, stay on Sonnet here.
- All three models (Haiku 4.5, Sonnet 4.6, Opus 4.7) selectable per slot.
- Cost-warning note below the dropdowns with rough per-scan dollar estimates and links to Anthropic's pricing + usage console.
Improvements
- Diagnostics → Run test uses Haiku unconditionally now (cheapest model) regardless of scan/chat settings — no reason to burn Sonnet/Opus tokens on a 16-token verify call.
Security
- Model-id values from
#__extensions.paramsare validated against the three-entry whitelist before being passed to the Anthropic API. If a future config-form bypass somehow stored an unexpected model id, calls fall through to Sonnet rather than echoing arbitrary user-controlled strings into the request payload.
v2.0.2 2026-04-29
Closes the v2.0.0 audit's I-9 trade-off (Anthropic API key visible on screen in component Options).
Security
- Anthropic API key is now blurred by default in the Options form, with a Reveal toggle to unmask. Custom form field
ApikeyFieldextends Joomla's standardTextField, applies a CSSfilter: blur(5px)to the input, and adds a Bootstrap input-group toggle button. Focusing the field also temporarily reveals it β useful for verifying a paste without committing to a sticky reveal. Underlying input staystype="text"so the key still round-trips at full length (thepassword-type truncation that bit us in v1.x doesn't come back). Avoids accidental shoulder-surfing exposure during screen shares, livestreams, or pair-debugging.
v2.0.1 2026-04-29
Closes the three findings from the v2.0.0 security review. No new features; tightening of existing controls.
Security
- Granular
cstemplateintegrity.viewACL action is now actually enforced for admin browsing. Previously a backend user withcore.manageon a different component could navigate directly to a session/backup URL and read the data without holding the granular action. Every adminHtmlView::display()now callsPermissionHelper::requireView(). (Closes L-2.) BackupDescriberescapes path segments internally before splicing them with literal—entities, so the helper's return value remains safe to render unescaped. Today's input flow is safe; this is defense in depth. (Closes M-1.)display.acknowledgeDisclaimernow callsPermissionHelper::requireView()for consistency with every other controller method. (Closes L-1.)
v2.0.0 2026-04-29
The whole automated-review-with-Claude path landed. v1.x exposed override data via REST and let your Claude session call back to apply fixes. v2.0 closes that loop: save your Anthropic API key, click Run automated scan, and the extension drives the entire review server-side — fetches every override, calls Claude, gets back a markdown report, saves it as a session. From the session view you can chat with Claude inline and have it apply fixes, dismiss findings, or clear the tracker.
New
- Run automated scan — one click on the dashboard drives the entire override review server-side using your saved Anthropic API key. No copy-paste prompt required. Caps at 60 overrides per call to stay within Anthropic's per-minute input-token budget.
- Chat with Claude on the session detail view. Submit a follow-up like “fix #1 and #3, dismiss the cosmetic ones” and the server runs an Anthropic tool-use loop with six tools wired to existing helpers (
apply_fix,dismiss_override,dismiss_all, etc.). Conversation persists turn-by-turn in a newmessagescolumn. Auto-backups still apply; everything Claude does is reversible. - Component Options dialog on the dashboard toolbar — one field for now (Anthropic API key), with the standard Joomla Permissions tab.
- Diagnostics modal with API-key fingerprint, system info, and a one-click Run test button that fires a tiny say PONG request to verify the saved key works.
- Loading-overlay system with spinner and elapsed-seconds counter. Locks the page during the 30–90s synchronous Anthropic calls so users don't navigate away or double-submit. Tracks Atum dark mode automatically.
- First-run "Before you start" disclaimer modal — per-admin acknowledgment, persists in the action log, surfaces backup advice and Tim's contact email.
- Sessions bulk download — tick rows in the session list and grab a single zip with one Markdown file per selected session.
- Plain-English file-purpose descriptions on every backup row.
Improvements
- Dashboard layout reworked — quick-nav button row at the top, Reset overrides moved up from the bottom, both prompt cards now lead with an audience-naming alert banner.
- Prompt boxes restyled with explicit dark-mode rules (
#0d1117background, GitHub-dark style), no-wrap so long lines scroll horizontally instead of leaving ragged hanging breaks, and a thicker border + slight inset shadow. - Disclaimer modal CSS now uses the dual
[data-bs-theme="dark"]/[data-color-scheme="dark"]selector pattern plus aprefers-color-scheme: darkfallback — reads correctly across every Joomla 5/6 admin template's flavor of dark mode. - Dashboard version display reads from the on-disk component manifest at render time. No more hardcoded version strings going stale.
- Top-level README rewritten with a prominent
/releases/latestdownload link at the top.
Build
- UTF-8 BOM detection in
build-package.ps1. Fails the build with a list of offending files if any.php/.xml/.iniunderpackages/has a BOM. Cannot ship a v1.0.2-style BOM regression again without going out of our way. - Schema migration in postflight — idempotent
ALTER TABLE ADD COLUMN messages LONGTEXTruns on every install/update, gated by a column-exists check. - Joomla 5 + Joomla 6 native declared explicitly via
<targetplatform name="joomla" version="5\.[0-9]+|6\.[0-9]+" />in every manifest.
Fixes
- Disclaimer "don't show again" was failing silently — inline JS posted the form token via URL query string, but
$this->checkToken()defaults to checking$_POST. Switched to$this->checkToken('get'). - Anthropic API key was being truncated to 99 chars at save time. Joomla's
passwordfield type was the culprit; switched totype="text"with explicitmaxlength="500"andfilter="raw". - HTTP 400 "Input should be a valid dictionary" when chatting with Claude. PHP's
json_decode($body, true)converts JSON{}to empty PHP arrays; re-encoding produces[], but Anthropic requirestool_use.inputto be an object.ConversationRunner::fixEmptyToolInputs()now walks every assistant turn and replaces empty arrays withstdClass. - Anthropic 10K-tokens-per-minute rate limit blew on chat continue because persisted scan messages carried the full ~60K-token override-file dump. Replaced with a short summary + tool-fetch-on-demand model.
- HTML entities in language strings (
—,“,…) replaced with literal UTF-8 characters;htmlspecialchars()-escaped strings were displaying—literally. - Dashboard prompt now lists write endpoints in the upfront Endpoints block with "THIS IS HOW YOU APPLY A PATCH" annotations — external Claude sessions had been reading the GET-only list and concluding the API was read-only.
- Postflight no longer renders the install-success card on uninstall.
Security
- Every new write endpoint (
display.runScan,display.testApiConnection,session.continueChat) is CSRF + ACL gated. - Tool-use fixes from chat run through the same path-safety guards as direct apply-fix calls — separator-anchored containment, PHP-extension whitelist,
opcache_invalidate()after every PHP write. - Anthropic API key never leaves the server. Read from
#__extensions.paramsper call, sent asx-api-keyheader, discarded.
Migration from 1.x
- 1.0.x → 2.0.0 is an in-place upgrade. Schema migration is idempotent.
- Sessions saved by the v1.0.4 build of the auto-scan had an oversized first user message; the first chat against one of those auto-rewrites it to a short summary on the fly.
v1.0.4 2026-04-29
Fixes
- Disclaimer modal in dark mode: card stayed white-on-bright in Atum dark mode because the CSS leaned only on Bootstrap CSS variables and didn't include explicit overrides for the
[data-bs-theme="dark"]/[data-color-scheme="dark"]selector pair the rest of the extension uses. Modal now mirrors the dual-selector pattern fromhighlight-theme.css, plus aprefers-color-scheme: darkmedia-query fallback. Email link in the modal body also picks up Bootstrap's link colour so it stays readable on the dark card.
v1.0.3 2026-04-29
Hotfix
- 1.0.2 produced an immediate "Compile Error: strict_types declaration must be the very first statement" 500 on every component view. The PowerShell pass during the 1.0.2 build saved seven template files with a UTF-8 BOM, which gets emitted as bytes before
<?phpparses and breaksdeclare(strict_types=1)'s "first statement" rule. All seven templates rewritten without BOM. Strongly recommend upgrading from 1.0.2 β 1.0.3 immediately; 1.0.2 is unusable.
v1.0.2 2026-04-29
New
- First-run "before you start" disclaimer modal: opens once per admin user the first time they enter any view of the extension. Tells them to take a full-site backup first, explains in plain English that the extension uses an AI (Claude) to review overrides and apply the fixes they confirm, reminds them AI can make mistakes, and offers
if they want help. "Don't show this again" checkbox persists per-user.This email address is being protected from spambots. You need JavaScript enabled to view it. - Per-user state is stored as a row in the existing
#__cstemplateintegrity_actionstable (action keydisclaimer_acknowledged) β no schema migration. When you hand a site to a client and they log in, they still see the warning the first time. - Modal renders identically across every component view (dashboard, sessions, session detail, sessionform, action log, backups list, backup detail) via a single helper call at the top of each template.
v1.0.1 2026-04-29
Improvements
- Joomla 5 + Joomla 6 native: every manifest (component, webservices plugin, package) now declares
<targetplatform name="joomla" version="5\.[0-9]+|6\.[0-9]+" />so the Joomla updater knows the extension is compatible with both. The code itself was already 5/6-native (services/provider.php DI, ApiController, JsonapiView, namespaced Factory/DatabaseInterface, no JFactory/JLog/JHtml legacy calls); this just makes it explicit to the installer. - Joomla update server wired up:
<updateservers>+<changelogurl>in the package manifest now point atupdates.xmlandCHANGELOG.htmlon the repo's main branch. Once 1.0.1 is installed, every future release will surface in System β Manage β Update automatically β no re-download from GitHub needed.
v1.0.0 2026-04-25
First stable release
Core loop β site owner pastes one prompt β Claude lists every flagged override on the site, classifies each one, writes a plain-English report, asks which to fix, applies the fixes the owner confirms, marks the rest as checked β has been live-tested end-to-end on a real client site running Joomla 6.1 on a third-party template.
What's in 1.0
- com_cstemplateintegrity (admin) β dashboard, sessions log, action log, file backups with restore, gated by ACL actions in
admin/access.xml. - plg_webservices_cstemplateintegrity β registers the
/api/index.php/v1/cstemplateintegrity/*routes; auto-enabled by the package installer. - API endpoints: GET
/overrides,/overrides/{id}/override-file,/overrides/{id}/core-file,/sessions/{id}; POST/overrides/{id}/apply-fix,/dismiss,/overrides/dismiss-all,/sessions,/backups/{id}/restore. - Auto-backup before every file write β every patch reversible from the admin UI or via the API.
- Same-chat conversational flow as the default; cross-session fix prompt as the rare-case helper.
- Plain-English descriptions on backup rows so non-technical users can tell at a glance what each file is.
- Unknown-finding catch-all β if a finding doesn't fit "code change" or "configuration question", Claude stops and explains in plain English instead of attempting a partial fix.
- claude.ai sandbox guidance built into the dashboard prompt (Settings β Capabilities β Code execution β Network access; close current chat and start a new one to pick up the updated allowlist).
Security baseline
admin/access.xmlwithcstemplateintegrity.view/.writeactions β every endpoint, admin and API, gated.- Separator-anchored path containment (no
strposprefix-collision bypass). - PHP-extension write whitelist β
.phpwrites only allowed undertemplates/<tpl>/html/. opcache_invalidate()after every PHP write so patches take effect immediately.- GET-form CSRF tokens on download links; CRLF/header-injection sanitization on
Content-Disposition. htmlspecialchars()on everyText::_()rendered into the installer frame.- No free-form
file_pathaccepted in any request body β all paths derived server-side from#__template_overridesrows.