Evaluate and integrate our Ultimate Multisite fork (El-SaMa/wp-multisite-waas)

FeatureOpenView on roadmap· 14 days ago

Imported from GitHub issue El-SaMa/lamoi-waas#5 by @El-SaMa.

Goal

Use what is solid in the fork (domain mapping, site templates and duplication, limits, host integrations), switch off what OMA owns (checkout, payments, invoices, customer emails), or decide to write a minimal own plugin.

Tasks

Sync the fork with upstream Ultimate-Multisite/ultimate-multisite (last push to our fork: Aug 2025); list the modules and which we keep.
Security review of the kept parts (REST endpoints, nonces, capability checks), PHPCS + Plugin Check zero issues (plugin definition of done).
White-label it: no plugin name, menus or emails visible to clients (#7).
Decide: install as-is, slimmed fork, or own plugin; write the decision into ADR 0001.
Note: the fork is a public repo; keep Lamoi-specific code and configuration in this private repo.

Acceptance criteria

Decision recorded; if kept, it runs on staging with checkout disabled and passes the hardening check.

Depends on

#4.

Plan key W5. Epic: El-SaMa/lamoi-waas#25.

Comments (0)

No comments yet.

Join the discussion