Skip to content

docs: say the account fixes and the Payment Methods repair shipped in v2.20.0 - #209

Draft
superdav42 wants to merge 1 commit into
mainfrom
docs/account-guide-fixed-in-v2-20-0
Draft

superdav42 wants to merge 1 commit into
mainfrom
docs/account-guide-fixed-in-v2-20-0

Conversation

@superdav42

Copy link
Copy Markdown
Contributor

Summary

Plugin release v2.20.0 was published at 22:03 UTC on 2026-11-21, 11 minutes before the previous docs PR merged. That PR's wording was written while the fixes were unreleased, so the deployed guides still say they "ship in the next release". This replaces that wording with the release.

Checked against the published release, not assumed:

  • The v2.20.0 tag contains both plugin PRs involved: their merge commits are ancestors of the tag.
  • The Payment Methods repair is in the tag. inc/ui/class-payment-methods-element.php calls get_public_title() at line 197, where v2.19.0 called the undefined get_title().
  • The payment editor in the tag shows Activate Membership? only for a pending payment (original_status === "pending") and has the add-on handling the guides describe.

Changes

  • frontend-account-page.md: the release note says the fixes were released in v2.20.0 and that v2.19.0 and earlier do not include them. The Payment Methods warning says it is fixed in v2.20.0. The Manual payment bullet and its troubleshooting row say "v2.20.0 and later" instead of "releases that include" the plugin PR.
  • frontend-account-blocks.md: the same release note and warning changes.
  • Two sentences are dropped because a release now exists: "the version string alone does not establish that those fixes are installed" and "do not install an unreleased development branch".

Statements about v2.19.0 and earlier are unchanged because they are still true: the Payment Methods fatal error from v2.4.12, the payment editor offering the toggle only for a Pending membership, and the membership editor route.

Verification

  • The three guides no longer contain "next release", "release that includes", "unreleased" or "merged to main".
  • The two admonition blocks still open and close correctly.
  • The docs build runs in this PR's checks.

Merging this redeploys the docs site (about 40 minutes).


aidevops.sh v3.39.189 plugin for OpenCode

… v2.20.0

Plugin release v2.20.0 was published at 22:03 UTC, 11 minutes before the
previous docs PR merged, so the deployed guides still say the fixes "ship in
the next release". Checked against the published tag: it contains both plugin
PRs involved, calls get_public_title() in the Payment Methods element where
v2.19.0 called the undefined get_title(), and its payment editor shows
"Activate Membership?" only for a pending payment and has the add-on handling.

Name the release in both guides: the fixes were released in v2.20.0, the
Payment Methods fatal error is fixed in v2.20.0, and the Manual payment
guidance says "v2.20.0 and later" instead of "releases that include" the
plugin PR. Drop the "version string alone does not establish" and "do not
install an unreleased development branch" sentences, which no longer apply.

Statements about v2.19.0 and earlier are unchanged, since they are still true.
@superdav42 superdav42 added the origin:interactive Auto-created by pulse labelless backfill (t2112) label Nov 21, 2026
@coderabbitai

coderabbitai Bot commented Nov 21, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

origin:interactive Auto-created by pulse labelless backfill (t2112)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant