| 开发者 | yoohw |
|---|---|
| 更新时间 | 2026年11月7日 13:31 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. An email address in an order, account or pasted list is not opt-in evidence. Without recorded evidence the status remains unknown. You can filter audiences by subscription status. Store managers are responsible for recording the appropriate permission for their messages. An existing unsubscribe always takes priority over a new subscription import.
It means the site's mail system accepted the handoff. It does not prove delivery to an inbox. Failed and unknown outcomes are shown separately. Only eligible known failures can be retried; unknown results are not automatically replayed.
Store-time scheduling uses the store timezone shown when composing the campaign. Recipient-local scheduling estimates a timezone only when the billing country has one supported timezone; missing or ambiguous location data uses UTC. This is a location estimate, not a confirmed customer preference. Manual lists use UTC. New schedules reject past times and local times that are missing or repeated because of daylight saving changes. They are not silently moved to another day. Confirmed UTC due times are preserved through pauses, retries and recovery; queue delays and limits may make actual sending later.
Confirmed content, recipients and scheduled times are saved for that campaign. Editing a draft or saved audience does not change it. Duplicate the campaign into a new draft to prepare another mailing, then preview and confirm again. Cancelled campaigns cannot be resumed.
Check its pause state, admission limit and queue diagnostics in Campaigns & Logs. Shared limits use fixed UTC minute/day windows; a reserved send slot may remain counted after an interrupted attempt. A working WordPress cron or queue worker is still required. The controls cannot recall mail already handed off.
The plugin stores campaign content, confirmed recipients, scheduling and delivery records, drafts, saved audience criteria, subscription evidence and opt-outs in your WordPress database. Emails are sent through the mail transport configured on your site. Subscription requests store the email, source, request/expiry time and a hashed confirmation token for at most 24 hours. Rate counters store hashes, not raw IP addresses. Confirmation requests are limited per address, client and site. A protected erased address is not re-enrolled or reconstructed by a new request. WordPress Tools > Export Personal Data and Erase Personal Data include this plugin's records for the requested email address, including guests. Erasure retains protective hashes and opt-out evidence to prevent reconstruction or another send. In-flight work or shared content in an active campaign may require another erasure pass after completion; the erasure result reports retained data. Retention is off by default (0 days). When enabled, hourly cleanup removes content, personal recipient details, snapshots and plugin queue arguments/logs from eligible finished campaigns after the configured period. Active campaigns, unfinished preparation and retryable work are excluded. Minimal campaign identifiers, email hashes, outcomes, claims, counters and suppression remain. Drafts and saved criteria remain until explicitly deleted or erased. This cleanup does not remove records held by mail providers, server logs or backups.
Deactivation cancels pending campaign work and removes the reconciliation event while retaining campaign records and opt-outs. Reactivation does not automatically restart cancelled work. When upgrading, stop background workers that have already loaded the old plugin code before replacing files. Version 0.4.0 keeps the existing plugin slug, text domain, settings, campaigns and opt-outs. Do not downgrade directly to 0.2.2, which does not understand the new cancellation and erasure protections. Data from the separate YoOhw Extra Code plugin is not imported automatically.
Yes. Use the yoohw-advanced-notifications text domain and the included languages/yoohw-advanced-notifications.pot template with Poedit or Loco Translate. Store compiled locale files in wp-content/languages/plugins/ to preserve them across updates. Administrator-written email content and saved messages are not translated automatically. Preserve placeholders such as %s, {customer_name} and {product_name}.