Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Standardize support text in block email templates#63463

Merged
pavel-mailpoet merged 3 commits intotrunkfrom
fix/standardize-block-email-support-text
Feb 27, 2026
Merged

Standardize support text in block email templates#63463
pavel-mailpoet merged 3 commits intotrunkfrom
fix/standardize-block-email-support-text

Conversation

@pavel-mailpoet
Copy link
Copy Markdown
Contributor

@pavel-mailpoet pavel-mailpoet commented Feb 27, 2026

Submission Review Guidelines:

Changes proposed in this Pull Request:

Standardize the closing support text across all customer-facing block email templates to a consistent message:

"Thanks again! If you need any help with your order, please contact us at {store email}."

Previously, each template had different closing text (e.g. "We hope to see you again soon", "If anything looks off…", "Please note that couriers may need some time…"). This unifies them per the design spec.

Closes https://linear.app/a8c/issue/WOOPRD-2478

How to test the changes in this Pull Request:

Enable the block email editor feature flag at:
WP Admin → WooCommerce → Settings → Advanced → Features
(check "Block email editor" and save).

Reset existing email templates: Reset templates first:

pnpm --filter=@woocommerce/plugin-woocommerce -- wp-env run cli bash -c "wp post delete \$(wp post list --post_type=woo_email --format=ids) --force && wp transient delete wc_email_editor_initial_templates_generated"

Then visit any WooCommerce admin page — the templates will be regenerated from the updated PHP files.

Create a test order (WP Admin → WooCommerce → Orders → Add new) with a customer that has an email address, then trigger email and verify the closing paragraph in Mailpit.

  • The closing paragraph reads exactly: "Thanks again! If you need any help with your order, please contact us at {store admin email}." (ending with a period, not a comma)
  • The {store admin email} placeholder is replaced with the actual store admin email address
  • No leftover old copy (e.g. "We hope to see you again soon", "If anything looks off…", etc.)

Milestone

Changelog entry

  • Automatically create a changelog entry from the details below.
Changelog Entry Details

Significance

  • Patch

Type

  • Update - Update existing functionality

Message

Standardize closing support text across all customer-facing block email templates.

Ensure all customer-facing order and fulfillment block email
templates use consistent closing text with the store email:
"Thanks again! If you need any help with your order, please
contact us at {store-email}."

Fixes trailing commas, missing "Thanks again!" prefix, and
replaces unrelated closing copy in fulfillment templates.
@github-actions github-actions Bot added the plugin: woocommerce Issues related to the WooCommerce Core plugin. label Feb 27, 2026
@woocommercebot woocommercebot requested a review from a team February 27, 2026 10:22
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 27, 2026

Testing Guidelines

Hi @triple0t ,

Apart from reviewing the code changes, please make sure to review the testing instructions (Guide) and verify that relevant tests (E2E, Unit, Integration, etc.) have been added or updated as needed.

Reminder: PR reviewers are required to document testing performed. This includes:

  • 🖼️ Screenshots or screen recordings.
  • 📝 List of functionality tested / steps followed.
  • 🌐 Site details (environment attributes such as hosting type, plugins, theme, store size, store age, and relevant settings).
  • 🔍 Any analysis performed, such as assessing potential impacts on environment attributes and other plugins, conducting performance profiling, or using LLM/AI-based analysis.

⚠️ Within the testing details you provide, please ensure that no sensitive information (such as API keys, passwords, user data, etc.) is included in this public issue.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 27, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7038900 and 0a6b42c.

📒 Files selected for processing (8)
  • plugins/woocommerce/templates/emails/block/customer-cancelled-order.php
  • plugins/woocommerce/templates/emails/block/customer-failed-order.php
  • plugins/woocommerce/templates/emails/block/customer-fulfillment-created.php
  • plugins/woocommerce/templates/emails/block/customer-fulfillment-deleted.php
  • plugins/woocommerce/templates/emails/block/customer-fulfillment-updated.php
  • plugins/woocommerce/templates/emails/block/customer-partially-refunded-order.php
  • plugins/woocommerce/templates/emails/block/customer-processing-order.php
  • plugins/woocommerce/templates/emails/block/customer-refunded-order.php
🚧 Files skipped from review as they are similar to previous changes (6)
  • plugins/woocommerce/templates/emails/block/customer-fulfillment-created.php
  • plugins/woocommerce/templates/emails/block/customer-failed-order.php
  • plugins/woocommerce/templates/emails/block/customer-partially-refunded-order.php
  • plugins/woocommerce/templates/emails/block/customer-cancelled-order.php
  • plugins/woocommerce/templates/emails/block/customer-refunded-order.php
  • plugins/woocommerce/templates/emails/block/customer-fulfillment-deleted.php

📝 Walkthrough

Walkthrough

Updates standardized closing/support text across multiple WooCommerce block email templates: adds "Thanks again!" to several messages, converts some static lines to translatable printf strings with a store-email placeholder, and fixes minor punctuation in a few translations.

Changes

Cohort / File(s) Summary
Printf-based store-email placeholder
plugins/woocommerce/templates/emails/block/customer-cancelled-order.php, plugins/woocommerce/templates/emails/block/customer-fulfillment-created.php, plugins/woocommerce/templates/emails/block/customer-fulfillment-deleted.php, plugins/woocommerce/templates/emails/block/customer-fulfillment-updated.php
Replaced static centered paragraph text with translatable printf strings that include the <!--[woocommerce/store-email]--> placeholder; added translator comments where applicable; bumped template @version to 10.7.0 in headers.
"Thanks again!" prepended to support line
plugins/woocommerce/templates/emails/block/customer-failed-order.php, plugins/woocommerce/templates/emails/block/customer-partially-refunded-order.php, plugins/woocommerce/templates/emails/block/customer-refunded-order.php
Prepended "Thanks again!" to the final contact sentence and normalized punctuation (added trailing period); retained store-email placeholder and translation wrappers; version bumps to 10.7.0 where present.
Punctuation/minor translation tweaks
plugins/woocommerce/templates/emails/block/customer-note.php, plugins/woocommerce/templates/emails/block/customer-processing-order.php
Minor punctuation changes in translated strings (comma → period or punctuation adjustments) with no control-flow changes.
Changelog entry
plugins/woocommerce/changelog/63463-fix-standardize-block-email-support-text
Added changelog entry noting the standardization of closing/support text across block email templates.

Sequence Diagram(s)

(omitted — changes are textual template updates without new multi-component control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: standardizing support text across block email templates, which is the primary focus of the PR.
Description check ✅ Passed The description is comprehensive and directly related to the changeset, explaining the standardization of closing support text across customer-facing block email templates with testing instructions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/standardize-block-email-support-text

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 27, 2026

Test using WordPress Playground

The changes in this pull request can be previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Test this pull request with WordPress Playground.

Note that this URL is valid for 30 days from when this comment was last updated. You can update it by closing/reopening the PR or pushing a new commit.

@pavel-mailpoet pavel-mailpoet requested review from triple0t and removed request for a team February 27, 2026 12:37
Copy link
Copy Markdown
Contributor

@triple0t triple0t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@triple0t triple0t assigned pavel-mailpoet and unassigned triple0t Feb 27, 2026
@pavel-mailpoet pavel-mailpoet merged commit 2aa0013 into trunk Feb 27, 2026
90 of 94 checks passed
@pavel-mailpoet pavel-mailpoet deleted the fix/standardize-block-email-support-text branch February 27, 2026 12:52
@github-actions github-actions Bot added this to the 10.7.0 milestone Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugin: woocommerce Issues related to the WooCommerce Core plugin.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants