Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Docs update: Ultimate Multisite v2.17.0

未关闭
#188 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
php, wordpress
领域
documentation

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

auto-dispatch documentation needs-update origin:interactive priority:medium status:available tier:standard

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. Reference inc/integrations/providers/gridpane/class-gridpane-integration.php in the plugin repo: WU_GRIDPANE_API_TOKEN (legacy WU_GRIDPANE_API_KEY alias), 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.txt 2.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.

主要语言
MDX
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Ultimate-Multisite/docs 的其他 Issue

查看 Ultimate-Multisite/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。