Docs update: Ultimate Multisite v2.17.0
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 68/100
- Tipo di issue
- Documentazione
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- php, wordpress
- Ambito
- documentation
Direzione di ricerca
Read the four listed guides first, preserving their frontmatter and style. Compare each statement with the merged plugin implementation, the referenced PRs, and the final readme.txt 2.17.0 changelog, then run the documentation repository's build and link checks from its package manifest. Done means verified user-facing behavior is accurately documented without speculative claims, credentials, or private paths.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Release context
Prepare manual documentation updates for Ultimate Multisite 2.17.0. Publication is authorized but still pending; do not describe the release as published until its GitHub/WordPress.org deployment is verified. The release aggregates already-merged changes since 2.16.1 and the checkout validation fix in Ultimate-Multisite/ultimate-multisite#1898.
Required updates
-
docs/user-guide/host-integrations/gridpane.md: verify and update setup for the current bearer-token API. Referenceinc/integrations/providers/gridpane/class-gridpane-integration.phpin the plugin repo:WU_GRIDPANE_API_TOKEN(legacyWU_GRIDPANE_API_KEYalias), optional site/server ID discovery during connection testing, legacy app-ID alias, optional DNS integration selection/ID, encrypted token storage and SSL/domain synchronization behavior. Do not request or embed actual credentials. -
docs/user-guide/configuration/checkout-forms.md: explain that existing WordPress accounts must authenticate before checkout links/logs in as that account; describe the multiple-memberships policy using the actual setting label/default from the plugin. Reference checkout ownership PR #1891 and membership policy PR #1880 in the plugin repo. -
docs/user-guide/administration/managing-memberships.md: update the relationship between repeat signup and the configured multiple-memberships policy. Clarify that restoring no-card trials preserves trial timing and applicable setup fees rather than immediately replacing the existing subscription. -
docs/user-guide/configuration/site-templates.md: assess whether template preparation/cloning guidance needs changes for plugin-owned initialization, duplicate-table handling and explicit clone failure reporting. Reference merged cloning changes and PR #1888 in the plugin repo. Add guidance only for verified user-facing behavior; do not invent new settings.
Reference pattern and verification
- These paths were verified in the current docs repository tree. Read each page first and preserve its existing frontmatter/style.
- Compare each statement with the merged plugin implementation and final
readme.txt2.17.0 changelog. Use the published tag once available, not an unmerged feature branch. - Check existing coverage before adding prose; skip a page with a brief explanation if it already accurately documents the behavior.
- Do not hand-edit generated hook references or addon changelog pages. Pure placeholder-formatting/internal test fixes do not require new manual guides.
- Run the docs repository's existing build/link checks using the commands declared by its own package manifest. Verify links and avoid retaining local/private paths or credentials.
Acceptance
Relevant guides accurately explain 2.17.0 behavior, with no speculative feature/configuration claims, and applicable docs validation passes. This documentation follow-up does not block shipping the already-tested customer-facing fixes.
aidevops.sh v3.34.13 plugin for OpenCode v1.18.31 with gpt-6.1-sol spent 1d 1h and 3,734,799 tokens on this with the user in an interactive session.
- Lingua principale
- MDX
- Stelle
- 0
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Ultimate-Multisite/docs
-
documentation needs-update origin:interactive status:available
Difficoltà 1/5 1-3 ore Idoneità per principianti 92/100
Ultimate-Multisite/docs#187 ·
-
documentation needs-update origin:interactive tier:standard
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
Ultimate-Multisite/docs#182 · 1 commento ·
-
documentation needs-update origin:interactive
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
Ultimate-Multisite/docs#173 ·
-
auto-dispatch consolidated documentation help wanted origin:worker status:available tier:standard
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
Ultimate-Multisite/docs#190 · 104 commenti ·
-
documentation needs-update
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
Ultimate-Multisite/docs#189 ·
Tutte le issue di Ultimate-Multisite/docs
Issue simili
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 91/100
alchaincyf/nuwa-skill#86 ·
-
Docs Needs Triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
pandas-dev/pandas#71055 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage release-watch
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 76/100
-
P1
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
SuruchBoss/Cwork#90 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100