958 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jmiller	6ad5046f82	Merge pull request 'chore(sync): cascade main -> dev' (#264) from main into dev	2026-07-13 08:47:20 +00:00
gitea-actions[bot]	20a760097b	chore(release): build 02.62.00 [skip ci]	2026-07-13 08:47:15 +00:00
jmiller	b378794a05	Merge pull request 'Release: dev → main (auto-continue checkbox + PHP 8.3)' (#263) from dev into main	2026-07-13 08:46:59 +00:00
mokogitea-actions[bot]	dc23f4dd5e	chore(version): pre-release bump to 02.61.06-dev [skip ci]	2026-07-13 01:52:14 +00:00
mokogitea-actions[bot]	9a5f4dbbb2	chore(version): pre-release bump to 02.61.05-dev [skip ci]	2026-07-13 01:51:29 +00:00
mokogitea-actions[bot]	45066237b0	chore(version): pre-release bump to 02.61.04-dev [skip ci]	2026-07-13 01:51:05 +00:00
jmiller	2296c2f754	Merge pull request 'fix: require PHP 8.3 (Joomla 6)' (#262) from fix/php83-v2 into dev	2026-07-13 01:47:12 +00:00
jmiller	7416c30925	@ ... docs: update CLAUDE.md MVC/DI notes from Joomla 4/5 to Joomla 6 Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 20:46:35 -05:00
jmiller	186a75681a	@ ... fix: require PHP 8.3 (Joomla 6) across code, composer, docs Joomla 6 requires PHP 8.3+, and the MokoGitea repo metadata php_minimum is 8.3, but the extension still enforced/declared 8.1: - DashboardModel health check: PHP_VERSION >= 8.1.0 -> 8.3.0 - MokoRestore preflight check: 8.1 -> 8.3 (hint now "Joomla 6 requires PHP 8.3+") - composer.json require php: >=8.1 -> >=8.3 - .mokogitea/CLAUDE.md: PHP 8.1+ -> 8.3+ (both places) Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 20:46:35 -05:00
jmiller	0a60436f3d	Merge pull request 'feat(runbackup): opt-in auto-continue + manual continue' (#261) from feat/runbackup-autocontinue into dev	2026-07-13 01:44:55 +00:00
jmiller	a2362d5400	@ ... feat(runbackup): opt-in auto-continue + manual continue on pre-update screen The pre-update/uninstall full-screen backup now shows an "Automatically continue the update when the backup finishes" checkbox (ticked by default, so the seamless flow is unchanged). If unticked, the screen stops on completion and offers a link to the new backup record plus a "Continue the update" button, so the user can hand back to Joomla manually — a reliable fallback when auto-continue does not fire. Also drop the hard-to-read `small` text class from the progress screen. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 20:44:10 -05:00
mokogitea-actions[bot]	6f1d270818	chore(version): pre-release bump to 02.61.01-dev [skip ci]	2026-07-13 01:02:13 +00:00
jmiller	7aa1f2eb43	Merge pull request 'chore(sync): cascade main -> dev' (#259) from main into dev	2026-07-13 01:01:57 +00:00
gitea-actions[bot]	4339c223a1	chore(release): build 02.61.00 [skip ci]	2026-07-13 00:58:56 +00:00
jmiller	cb56430e37	Merge pull request 'Release: dev → main (runbackup CSS fixes)' (#258) from dev into main	2026-07-13 00:58:38 +00:00
mokogitea-actions[bot]	67611604e2	chore(version): pre-release bump to 02.60.06-dev [skip ci]	2026-07-13 00:58:35 +00:00
gitea-actions[bot]	00c1add0cd	chore(version): auto-bump patch 02.60.05-dev [skip ci]	2026-07-13 00:58:23 +00:00
jmiller	1e3f963beb	Merge remote-tracking branch 'origin/dev' into dev	2026-07-12 19:58:07 -05:00
jmiller	c280229b90	@ ... chore: back-merge main into dev (reconcile release version stamps) Absorbs main (previous release) into dev ahead of the next release. All conflicts were VERSION-stamp comments/tags in manifests, SECURITY.md and issue-branch.yml — kept dev's current line. No functional changes. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 19:57:54 -05:00
mokogitea-actions[bot]	fbf0a2de76	chore(version): pre-release bump to 02.60.04-dev [skip ci]	2026-07-13 00:54:57 +00:00
jmiller	30b8e66eca	Merge pull request 'style(runbackup): gray card via bg-body-secondary class' (#257) from style/runbackup-card-bg-class into dev	2026-07-13 00:54:14 +00:00
jmiller	83b261db02	@ ... style(runbackup): gray card via bg-body-secondary utility class Move the card background off a custom CSS rule and onto a Bootstrap utility class (bg-body-secondary) on the card element itself, so the gray panel background is declared in the markup. Supersedes the .card background-color rule added in the previous change. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 19:54:01 -05:00
mokogitea-actions[bot]	e0285f112f	chore(version): pre-release bump to 02.60.03-dev [skip ci]	2026-07-13 00:52:32 +00:00
jmiller	f5538ade88	Merge pull request 'style(runbackup): gray card panel' (#256) from style/runbackup-gray-card into dev	2026-07-13 00:52:15 +00:00
jmiller	2d27385ac9	@ ... style(runbackup): gray card panel on the black backdrop Set the backup card (.msb-runbackup > .card) to a gray background so it reads as a panel against the black full-screen backdrop instead of stark white. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 19:52:06 -05:00
mokogitea-actions[bot]	a3eb713d81	chore(version): pre-release bump to 02.60.02-dev [skip ci]	2026-07-13 00:06:00 +00:00
jmiller	7106ece393	Merge pull request 'fix(css): reliably load component stylesheets (progress bar unstyled)' (#255) from fix/runbackup-css-load into dev	2026-07-13 00:05:45 +00:00
mokogitea-actions[bot]	394ad0d607	chore(version): pre-release bump to 02.60.01-dev [skip ci]	2026-07-13 00:05:33 +00:00
jmiller	f5bcc7c457	@ ... fix(css): reliably load component stylesheets (progress bar was unstyled) The full-screen backup progress bar lost all styling after the CSS moved to the Web Asset Manager: this component's WAM style assets do not emit a <link> on the admin document. The asset resolves without error (Joomla lazily registers media/com_mokosuitebackup/joomla.asset.json, so useStyle does not throw) yet no stylesheet tag is rendered — and the same was already silently true of com_mokosuitebackup.admin (it was just cosmetic, so unnoticed). Confirmed live: neither runbackup.css nor admin.css loads, body stays white, the bar has no track/fill. Attach the external media stylesheets directly to the document (addStyleSheet), which renders reliably via <jdoc:include type="styles">. The joomla.asset.json + useStyle calls are kept so the WAM path resumes automatically if/when it starts emitting. Fixes both runbackup and the profile edit screen. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 19:05:15 -05:00
gitea-actions[bot]	69c70d4480	chore(release): build 02.60.00 [skip ci]	2026-07-12 23:33:41 +00:00
jmiller	89f1869120	Merge pull request 'Release: dev → main (02.59.x)' (#253) from dev into main	2026-07-12 23:33:28 +00:00
mokogitea-actions[bot]	0c845fe807	chore(version): pre-release bump to 02.59.09-dev [skip ci]	2026-07-12 23:33:14 +00:00
jmiller	a60f7ac032	Merge pull request 'docs(ajax): correct preupdateAck docblock' (#254) from docs/preupdateack-docblock into dev	2026-07-12 23:33:00 +00:00
jmiller	f62b1ec72e	@ ... docs(ajax): correct preupdateAck docblock to one-shot skip semantics The docblock still described the removed 10-minute throttle ("arms BOTH keys"). It now sets a one-shot, action-keyed skip flag consumed once by the system plugin. Comment-only; no behaviour change. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 18:28:54 -05:00
mokogitea-actions[bot]	0562d3effd	chore(version): pre-release bump to 02.59.08-dev [skip ci]	2026-07-12 23:25:09 +00:00
gitea-actions[bot]	1c5c511c06	chore(version): auto-bump patch 02.59.07-dev [skip ci]	2026-07-12 23:24:59 +00:00
jmiller	444cfa3fdb	Merge remote-tracking branch 'origin/dev' into dev	2026-07-12 18:24:40 -05:00
jmiller	1e6d9ba078	@ ... chore: back-merge main into dev (release 02.59.00 version stamps) Reconciles main (released 02.59.00) into dev ahead of the next release. All conflicts were VERSION-stamp comments/tags in manifests, SECURITY.md and issue-branch.yml — kept dev's current 02.59.05 line. No functional changes. Clears the dev -> main merge conflict for the release PR. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 18:24:12 -05:00
mokogitea-actions[bot]	9ee800b151	chore(version): pre-release bump to 02.59.06-dev [skip ci]	2026-07-12 23:18:54 +00:00
jmiller	25991c474b	Merge pull request 'refactor(runbackup): move screen CSS into the Web Asset Manager' (#252) from fix/runbackup-css-wam into dev	2026-07-12 23:18:41 +00:00
mokogitea-actions[bot]	059cbfe058	chore(version): pre-release bump to 02.59.05-dev [skip ci]	2026-07-12 23:18:27 +00:00
jmiller	d658019007	@ ... refactor(runbackup): move screen CSS into the Web Asset Manager All full-screen backup CSS now loads through Joomla WAM instead of an inline <style> block (and the redundant inline style="width:0"): - New media/css/runbackup.css holds the whole stylesheet. - Registered as asset com_mokosuitebackup.runbackup in joomla.asset.json. - tmpl/runbackup/default.php loads it via getDocument()->getWebAssetManager()->useStyle(com_mokosuitebackup.runbackup), matching the existing com_mokosuitebackup.admin pattern. The css folder already ships via the manifest <folder>css</folder>, so no manifest change is needed. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 18:18:08 -05:00
mokogitea-actions[bot]	8237f85056	chore(version): pre-release bump to 02.59.04-dev [skip ci]	2026-07-12 23:14:28 +00:00
jmiller	14cc00f93f	Merge pull request 'style(runbackup): black backdrop on the full-screen backup screen' (#251) from fix/runbackup-black-bg into dev	2026-07-12 23:14:15 +00:00
mokogitea-actions[bot]	d1ccb8d419	chore(version): pre-release bump to 02.59.03-dev [skip ci]	2026-07-12 23:14:09 +00:00
jmiller	8a783aa25a	@ ... style(runbackup): black backdrop on the full-screen backup screen Set html/body background to #000 so the full-screen pre-update / Backup Now progress screen runs on a black backdrop (the card + Atum-coloured progress bar sit on top). Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 18:13:51 -05:00
mokogitea-actions[bot]	d9d6ee9181	chore(version): pre-release bump to 02.59.02-dev [skip ci]	2026-07-12 22:48:45 +00:00
jmiller	f02c4d4c9d	Merge pull request 'fix: pre-action backup fires for every extension (not one per 10 min)' (#250) from fix/preaction-per-action-backup into dev	2026-07-12 22:48:33 +00:00
mokogitea-actions[bot]	2df4b280eb	chore(version): pre-release bump to 02.59.01-dev [skip ci]	2026-07-12 22:48:27 +00:00
jmiller	3eb2562abd	@ ... fix: pre-action backup fires for every extension, not one per 10 min Root cause of "pre-update backup only fires on the backup extension": a coarse 600s session throttle. Whenever ANY pre-action backup ran (including updating MokoSuiteBackup itself, or a core Joomla update), the key mokosuitebackup.preaction_backup_before_update was armed for 10 minutes. onBeforeCompileHead read it as `recentBackup` and DISABLED the client-side interceptor for all extensions, and runPreActionBackup was throttled by the same window. So after updating one extension, every other extension update silently skipped its backup for 10 minutes. Replace the time window with "one backup per Update action": - runPreActionBackup dedupes per-request (a batch update fires the event once per extension in a single request -> back up once) via instance flags, and consumes a ONE-SHOT session skip flag for the re-fired client update/uninstall (skip once, next distinct action backs up). - ajax.preupdateAck sets the one-shot flag for the SPECIFIC action (update|uninstall), passed from installer-backup.js via &msb_action and surfaced by Runbackup HtmlView -> CFG.action. A core update passes no action, so it never suppresses an extension backup. - onBeforeCompileHead drops the recentBackup time-suppression (the re-fire loop is already guarded client-side by window.__msbResuming). - The core Joomla update path uses its own key (mokosuitebackup.core_update_backed_up), decoupled from extensions. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i @	2026-07-12 17:48:09 -05:00