← Back to Baseline

MB-0809

Partially automated Supported module XML satisfies its local schema

MB-C20 Module Integrity & Compatibility Medium

Collected module, routes, webapi and ACL XML declarations satisfy their resolvable project-local declared Magento XSD.

Overview

Resolve each declared XSD against the installed project, then review module, routes, webapi and ACL XML validation errors. An unavailable XSD leaves validation unresolved.

Why it Matters

Invalid XML can prevent intended module configuration from being understood by the installed release.

Interpret the reported resource and collection scope before making changes. Unsupported source, unresolved symbols and bounded collection gaps cannot establish a clean result.

Verification Steps

Manual Verification

  1. Resolve each declared XSD against the installed project, then review module, routes, webapi and ACL XML validation errors. An unavailable XSD leaves validation unresolved.
  2. Inspect the reported file, declaration, package or evidence record in the same selected release. Keep source observations separate from effective runtime behavior.
  3. Apply the rule-specific remediation below, validate the affected behavior in staging, and rerun the same selection.

Command / Review Sample

php magebean.phar audit --path=/var/www/magento --profile=module-integrity --rules=MB-0809 --modules=Vendor_Module

Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.

Remediation / Fix Guidance

  1. Correct the document using the installed release schema.
  2. Verify the corrected behavior in an authorized staging environment.
  3. Rerun MB-0809 with the same module selection.

Examples

Illustrative declaration/review examples, not recorded scan output. A pass example concerns only the stated predicate and supported collected scope.

Fail Example

webapi.xml contains an element rejected by its resolved installed XSD.

Pass Example

Collected webapi.xml validates against its resolved installed XSD.
This establishes schema validity only.

Scope and Evidence Limits

Rule revision: 1. Target modes: LOCAL.

Collected module, routes, webapi and ACL XML declarations satisfy their resolvable project-local declared Magento XSD.

A missing schema or unparseable document is a collection gap. Effective XML merge behavior is outside this predicate.

Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.

References