Docs update: Ultimate Multisite v2.14.2
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start by reading docs/developer/rest-api/overview.md and docs/user-guide/troubleshooting/how-to-get-help.md. Document the authenticated site-availability-diagnose tool, its supported inputs and returned fields, then add the v2.14.2 troubleshooting note. Done means both listed documentation updates accurately cover the release behavior.
Written by the indexing model from the issue text.
Description
Release
Ultimate Multisite v2.14.2 — released 2026-07-16
Required doc updates
-
docs/developer/rest-api/overview.md— document the authenticated MCP/ability toolmultisite-ultimate/site-availability-diagnose, including supported inputs (site_id,domain, optionalfrontend_smoke) and returned availability, targeting, domain mapping, visit-limit, and lock-reason fields. -
docs/user-guide/troubleshooting/how-to-get-help.md— add a support note that v2.14.2 site availability diagnostics can help identify domain mapping, membership lock, demo/inactive site, and visit-limit lock reasons.
Changelog entry
Version [2.14.2] - Released on 2026-07-16
- New: Authenticated site availability diagnostics now report domain, lock, visit-limit, and frontend smoke-test details for support and automation.
- Fix: Cross-domain SSO now preserves the correct admin destination and handles cookie-less token redirects more safely.
- Fix: Visit-limit lock pages now return HTTP 503, blank screenshots are rejected, and MU-Migration WP-CLI probes no longer trigger autoload errors.
- Fix: Shortcode generator fields, late add-on forms, and default template availability now load reliably.
Auto-generated by /wp-release
- Dominant language
- MDX
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Ultimate-Multisite/docs
-
documentation needs-update origin:interactive status:available
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Ultimate-Multisite/docs#187 ·
-
documentation needs-update origin:interactive tier:standard
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Ultimate-Multisite/docs#182 · 1 comment ·
-
documentation needs-update origin:interactive tier:standard
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Ultimate-Multisite/docs#186 · 1 comment ·
-
auto-dispatch documentation needs-update origin:interactive status:available tier:standard
Difficulty 3/5 1-2 days Newbie friendliness 84/100
Ultimate-Multisite/docs#185 ·
-
documentation needs-update origin:interactive tier:standard
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Ultimate-Multisite/docs#184 · 1 comment ·
All issues in Ultimate-Multisite/docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·