feat: validate Joomla metadata against package/component XML manifest #257

New Issue

2026-06-18T20:12:52Z

jmiller commented

2026-06-18 20:12:52 +00:00

Problem

MokoGitea repo metadata (.mokogitea/manifest.xml) drives the update server feed (updates.xml). If the metadata doesn't match the actual Joomla package/component XML manifest, updates break silently — the <element>, <type>, and <client> in the feed won't match what Joomla registers in #__extensions.

This mismatch blocked MokoSuiteBackup updates for days before it was caught manually.

Proposed Feature

Add a moko validate:joomla-metadata CLI command that:

Reads the MokoGitea repo metadata (via API or .mokogitea/manifest.xml)
Reads the Joomla manifest XML (e.g. source/pkg_mokosuitebackup.xml or source/packages/com_mokosuitebackup/mokosuitebackup.xml)
Compares critical fields and reports mismatches

Fields to validate

Metadata Field	Joomla XML Source	Match Rule
`package_type`	`<extension type=\"...\">`	Must match (package, component, module, etc.)
element name (derived)	`<packagename>` / `<element>` / `<name>`	Must match Joomla's element derivation logic
`display_name`	`<name>` tag	Should match
`version`	`<version>` tag	Should match (warn if different)
`php_minimum`	composer.json `require.php`	Should match
`target_version`	`<targetplatform version>` in update XML	Should match pattern
`description`	`<description>` tag	Should match

Output example

$ moko validate:joomla-metadata

Validating MokoSuiteBackup metadata...

  package_type: package ✓ (matches <extension type=\"package\">)
  element:      pkg_mokosuitebackup ✓ (derived from package + mokosuitebackup)
  display_name: Package - MokoSuiteBackup ✓
  version:      01.22.09-dev ✓
  php_minimum:  8.1 ✓ (matches composer.json)

  ✓ All checks passed

Error example

  element:      MokoSuiteBackup ✗ (expected pkg_mokosuitebackup)
    Fix: Set package_type to \"package\" in .mokogitea/manifest.xml

  ✗ 1 mismatch found — update delivery will fail

Integration

Should be callable standalone: moko validate:joomla-metadata
Should also be callable from CI workflows (exit code 1 on failure)
The Template-Joomla repo should add this as a step in ci-joomla.yml and pr-check.yml

## Problem MokoGitea repo metadata (`.mokogitea/manifest.xml`) drives the update server feed (`updates.xml`). If the metadata doesn't match the actual Joomla package/component XML manifest, updates break silently — the `<element>`, `<type>`, and `<client>` in the feed won't match what Joomla registers in `#__extensions`. This mismatch blocked MokoSuiteBackup updates for days before it was caught manually. ## Proposed Feature Add a `moko validate:joomla-metadata` CLI command that: 1. Reads the MokoGitea repo metadata (via API or `.mokogitea/manifest.xml`) 2. Reads the Joomla manifest XML (e.g. `source/pkg_mokosuitebackup.xml` or `source/packages/com_mokosuitebackup/mokosuitebackup.xml`) 3. Compares critical fields and reports mismatches ### Fields to validate | Metadata Field | Joomla XML Source | Match Rule | |---|---|---| | `package_type` | `<extension type=\"...\">` | Must match (package, component, module, etc.) | | element name (derived) | `<packagename>` / `<element>` / `<name>` | Must match Joomla's element derivation logic | | `display_name` | `<name>` tag | Should match | | `version` | `<version>` tag | Should match (warn if different) | | `php_minimum` | composer.json `require.php` | Should match | | `target_version` | `<targetplatform version>` in update XML | Should match pattern | | `description` | `<description>` tag | Should match | ### Output example ``` $ moko validate:joomla-metadata Validating MokoSuiteBackup metadata... package_type: package ✓ (matches <extension type=\"package\">) element: pkg_mokosuitebackup ✓ (derived from package + mokosuitebackup) display_name: Package - MokoSuiteBackup ✓ version: 01.22.09-dev ✓ php_minimum: 8.1 ✓ (matches composer.json) ✓ All checks passed ``` ### Error example ``` element: MokoSuiteBackup ✗ (expected pkg_mokosuitebackup) Fix: Set package_type to \"package\" in .mokogitea/manifest.xml ✗ 1 mismatch found — update delivery will fail ``` ## Integration - Should be callable standalone: `moko validate:joomla-metadata` - Should also be callable from CI workflows (exit code 1 on failure) - The Template-Joomla repo should add this as a step in `ci-joomla.yml` and `pr-check.yml` ## Related - MokoGitea-Fork #635 — element name derivation fix - MokoGitea-Fork PR #643 — lowercase + clean element names

jmiller commented

2026-06-18 20:12:53 +00:00

Branch created: feature/257-feat-validate-joomla-metadata-against-pa

git fetch origin
git checkout feature/257-feat-validate-joomla-metadata-against-pa

Branch created: [`feature/257-feat-validate-joomla-metadata-against-pa`](https://git.mokoconsulting.tech/MokoConsulting/mokoplatform/src/branch/feature/257-feat-validate-joomla-metadata-against-pa) ```bash git fetch origin git checkout feature/257-feat-validate-joomla-metadata-against-pa ```

jmiller referenced this issue from a commit

2026-06-18 20:53:46 +00:00

feat: add joomla_metadata_validate CLI command (#257)

jmiller referenced this issue

2026-06-18 20:54:02 +00:00

feat: joomla_metadata_validate CLI command (#257) #258

jmiller referenced this issue from a commit

2026-06-18 20:55:17 +00:00

Merge pull request 'feat: joomla_metadata_validate CLI command (#257)' (#258) from feature/257-joomla-metadata-validate into main

jmiller referenced this issue from a commit

2026-06-19 08:13:54 +00:00

feat: add joomla_metadata_validate CLI command (#257)