816 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jmiller	97e8d0cbe9	fix(ui): WAM-loaded CSS, per-destination keep-local, tidy destination modal ... - Move component admin CSS to the Joomla Web Asset Manager: new media/com_mokosuitebackup/css/admin.css + media/joomla.asset.json, a <media> entry in the manifest, and useStyle('com_mokosuitebackup.admin') in the profile edit view. Removes the inline <style> block (no more inline CSS). - Remove the profile-level "Keep local copy" field/"Remote" fieldset from forms/profile.xml — it is now per remote destination (modal remoteKeepLocal). - Clean up the Add/Edit Destination modal padding/margins (in admin.css). Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 18:48:33 -05:00
mokogitea-actions[bot]	8d5b33a74d	chore(version): pre-release bump to 02.57.06-dev [skip ci]	2026-07-05 23:32:04 +00:00
jmiller	77bfaff8cd	Merge pull request 'fix(installer): self-heal admin menu + alias collision + short-constant label' (#219) from fix/admin-menu-selfheal into dev	2026-07-05 23:31:41 +00:00
mokogitea-actions[bot]	1c420b2277	chore(version): pre-release bump to 02.57.05-dev [skip ci]	2026-07-05 23:31:24 +00:00
jmiller	2af2641712	fix(installer): self-heal admin menu; fix alias collision; short-constant label ... Fallout of the duplicate-component element bug: - Preflight now runs removeOrphanedComponent() BEFORE the component install recreates its menu, so the orphan's "Backup" menu (alias "backup") no longer collides ("The alias backup is already being used by the Backup menu item"). - ensureSubmenuItems() recreates the top-level "Backup" menu when it is missing (via new createTopMenu()) instead of bailing out — so a failed install that deleted the parent menu no longer leaves Backup gone from the admin menu (which also broke the cPanel module and MokoSuiteClient component detection). - The top-level menu label now uses the short constant COM_MOKOJOOMBACKUP_SHORT (manifest <menu> + enforced/normalized in the script). Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 18:31:06 -05:00
mokogitea-actions[bot]	a3c7183374	chore(version): pre-release bump to 02.57.04-dev [skip ci]	2026-07-05 23:15:31 +00:00
jmiller	4f91d1e432	Merge pull request 'chore(sync): cascade main -> dev' (#212) from main into dev	2026-07-05 23:03:57 +00:00
jmiller	604412f82f	Merge chore/normalize-docs: normalize doc/config refs	2026-07-05 22:50:52 +00:00
jmiller	94ff15c128	chore(docs): normalize refs — MokoStandards->org wiki, moko-platform->mokocli, residual MokoGitea/MokoSuite ... Non-workflow docs/config only (CLAUDE.md, README, branch-protection, ISSUE_TEMPLATE/config.yml, ci-issue-reporter). Workflow files, manifest schema, and Makefile install paths left for the forge-rebrand gate. Authored-by: Moko Consulting	2026-07-05 22:50:50 +00:00
mokogitea-actions[bot]	a92f423767	chore(version): pre-release bump to 02.57.02-dev [skip ci]	2026-07-05 22:44:13 +00:00
jmiller	ba2cda1385	Merge pull request 'fix(installer): drop legacy remote columns in PHP, not PREPARE-based SQL' (#218) from fix/sql-prepared-statement-protocol into dev	2026-07-05 22:43:53 +00:00
mokogitea-actions[bot]	72aeea6955	chore(version): pre-release bump to 02.57.01-dev [skip ci]	2026-07-05 22:41:55 +00:00
jmiller	8a85370e32	fix(installer): drop legacy remote columns in PHP, not PREPARE-based SQL ... 02.56.01.sql used PREPARE/EXECUTE/DEALLOCATE to conditionally drop the 26 legacy remote_storage/ftp_*/sftp_*/gdrive_*/s3_* columns portably. Joomla's installer rejects those statements on MySQL 8 (error 1295: "This command is not supported in the prepared statement protocol yet"), aborting the whole component install when updating from an old schema. Neutralize 02.56.01.sql (now a no-op comment) and move the purge into Pkg_MokoSuiteBackupInstallerScript::dropLegacyRemoteColumns(): gate on INFORMATION_SCHEMA, then issue one plain ALTER dropping only the columns that still exist — portable on MariaDB and MySQL 8, idempotent, non-fatal. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:41:26 -05:00
gitea-actions[bot]	ea91b49e50	chore(release): build 02.57.00 [skip ci]	2026-07-05 22:30:31 +00:00
jmiller	99d8e954bd	Merge pull request 'feat: BackupRunner helper — unify backup run/status/notification' (#214) from feat/backup-runner-helper into main	2026-07-05 22:29:38 +00:00
jmiller	28ca110d7b	docs(changelog): add BackupRunner entry (#214) ... Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:29:28 -05:00
jmiller	307067580c	feat: BackupRunner helper — unify backup run/status/notification ... Every non-interactive backup trigger used a slightly different path, so final status and notification gating behaved inconsistently depending on what started the backup (this is why pre-update backups did not gate notifications the way "Backup Now" does). Add src/Service/BackupRunner.php as the single synchronous entry point. It delegates to BackupEngine (which already sends notifications gated by the profile's notify_on_success/notify_on_failure and applies retention — so there is exactly ONE notification layer), and normalises the result, including the real complete/warning/fail status the engine records but did not return. BackupRunner self-loads BackupEngine so callers require one file. Routed through BackupRunner: - plg_system runPreActionBackup() (preaction) + web-cron handler (webcron) - plg_content triggerAutoBackup() (pre-install) - plg_task scheduled task run - plg_console RunCommand (cli) The dashboard AJAX/stepped "Backup Now" flow is unchanged (it is the interactive equivalent). The installer progress popup is deferred — the installer request cannot drive the AJAX modal (TODO(#196) noted in code). php -l clean on all changed files. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:28:59 -05:00
jmiller	7f5f041588	Merge pull request 'fix(release): idempotent changelog promote (no duplicate version headers)' (#217) from fix/changelog-promote-idempotent into main	2026-07-05 22:28:19 +00:00
jmiller	129be7ef9d	fix(release): idempotent changelog promote + dedupe 02.56.11 header ... Guard the promote so it only inserts a version header when absent (stops the empty duplicate headers each build was appending), and remove the duplicate 02.56.11 header the non-idempotent promote just created. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:28:08 -05:00
jmiller	14392de078	Merge pull request 'docs(changelog): backfill 02.56.07 + 02.56.08 (shipped with empty changelogs)' (#215) from fix/changelog-backfill into main	2026-07-05 22:26:17 +00:00
jmiller	8bdadb68c2	docs(changelog): backfill 02.56.07/08 + dedupe blank duplicate headers ... Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:26:05 -05:00
gitea-actions[bot]	bcc4054ced	chore: promote changelog [Unreleased] → [02.56.11]	2026-07-05 22:23:35 +00:00
gitea-actions[bot]	0cba7f81e8	chore(release): build 02.56.11 [skip ci]	2026-07-05 22:23:26 +00:00
jmiller	2688ea352b	Merge pull request 'fix(installer): self-heal orphaned com_component-mokosuitebackup on update' (#216) from fix/orphan-component-cleanup into main	2026-07-05 22:23:08 +00:00
mokogitea-actions[bot]	39d94a31d6	chore(version): pre-release bump to 02.56.11-dev [skip ci]	2026-07-05 22:14:22 +00:00
jmiller	1029e40908	fix(installer): self-heal orphaned com_component-mokosuitebackup on update ... The old "Type - Name" component <name> made Joomla register a duplicate component under element com_component-mokosuitebackup (its own extension row, admin menu, schema rows and administrator/ folder), orphaning the real com_mokosuitebackup on the old version. The manifest fix (#213) prevents new occurrences; this reconciles already-affected sites automatically. Package postflight now removes any component whose element matches %component%mokosuitebackup% (excluding com_mokosuitebackup): deletes its #__menu, #__schemas and #__update_sites_extensions rows, the #__extensions record, and the stray admin folder. Idempotent and non-fatal. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 17:11:51 -05:00
gitea-actions[bot]	ec3094385f	chore: promote changelog [Unreleased] → [02.56.08]	2026-07-05 22:02:08 +00:00
gitea-actions[bot]	4a2bb1b19d	chore(release): build 02.56.08 [skip ci]	2026-07-05 22:01:48 +00:00
jmiller	3c5ad43e97	Merge pull request 'fix(manifest): component &lt;name&gt; must be element-safe (com_mokosuitebackup)' (#213) from fix/component-element-name into main	2026-07-05 22:01:17 +00:00
mokogitea-actions[bot]	f92e5227dc	chore(version): pre-release bump to 02.56.08-dev [skip ci]	2026-07-05 21:58:57 +00:00
jmiller	9db54ac60c	fix(manifest): component <name> must be element-safe (com_mokosuitebackup) ... The "Type - Name" convention (commit d155958) set the component <name> to "Component - MokoSuiteBackup". Joomla derives a component's element from its <name> (com_ + sanitized name), so this produced element `com_component-mokosuitebackup` instead of `com_mokosuitebackup`. On update, Joomla registered a NEW component (new element + folder) at the current version and orphaned the real `com_mokosuitebackup` at its old version — which is what `?option=com_mokosuitebackup` and the admin menu still load. Net effect: the component appears "stuck" on the old version with the old UI. Revert the component <name> to "MokoSuiteBackup" (-> com_mokosuitebackup) and document why the display convention must not be applied to a component's <name>. Packages are exempt (they use <packagename>); plugins/modules are exempt (<name> is only a display label there). Refs #171-area remote tab reports; fixes the duplicate-component registration. Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i	2026-07-05 16:58:37 -05:00
jmiller	0c7c3552ed	chore: sync workflow-sync-trigger.yml from Template-Generic [skip ci]	2026-07-05 21:49:42 +00:00
jmiller	351321161a	chore: sync version-set.yml from Template-Generic [skip ci]	2026-07-05 21:49:40 +00:00
jmiller	d2cc234fce	chore: sync repo-health.yml from Template-Generic [skip ci]	2026-07-05 21:49:37 +00:00
jmiller	2389df8670	chore: sync rc-revert.yml from Template-Generic [skip ci]	2026-07-05 21:49:34 +00:00
jmiller	55f29498b0	chore: sync pre-release.yml from Template-Generic [skip ci]	2026-07-05 21:49:31 +00:00
jmiller	a5397c0f16	chore: sync pr-check.yml from Template-Generic [skip ci]	2026-07-05 21:49:28 +00:00
jmiller	c0792a6ba0	chore: sync notify.yml from Template-Generic [skip ci]	2026-07-05 21:49:26 +00:00
jmiller	7a3f0f914e	chore: sync issue-branch.yml from Template-Generic [skip ci]	2026-07-05 21:49:24 +00:00
jmiller	cc7f18ae45	chore: sync gitleaks.yml from Template-Generic [skip ci]	2026-07-05 21:49:22 +00:00
jmiller	4cf8f8243d	chore: sync cleanup.yml from Template-Generic [skip ci]	2026-07-05 21:49:20 +00:00
jmiller	efb28fa386	chore: sync ci-issue-reporter.yml from Template-Generic [skip ci]	2026-07-05 21:49:17 +00:00
jmiller	68043c9a37	chore: sync ci-generic.yml from Template-Generic [skip ci]	2026-07-05 21:49:15 +00:00
jmiller	e5558fad26	chore: sync cascade-dev.yml from Template-Generic [skip ci]	2026-07-05 21:49:12 +00:00
jmiller	60c5c00333	chore: sync branch-cleanup.yml from Template-Generic [skip ci]	2026-07-05 21:49:10 +00:00
jmiller	f9169fd9f7	chore: sync auto-release.yml from Template-Generic [skip ci]	2026-07-05 21:49:07 +00:00
jmiller	d69db6fac3	chore: sync auto-bump.yml from Template-Generic [skip ci]	2026-07-05 21:49:05 +00:00
gitea-actions[bot]	1f7c2ef1ba	chore: promote changelog [Unreleased] → [02.56.07]	2026-07-05 21:34:17 +00:00
gitea-actions[bot]	24d7dc0064	chore(release): build 02.56.07 [skip ci]	2026-07-05 21:34:06 +00:00
jmiller	f4bc1d128c	Merge pull request 'fix: security + data-integrity fixes (P0/P1)' (#211) from fix/security-integrity-p0p1 into main	2026-07-05 21:33:49 +00:00