NewsletterPlatform.com 1.0.9 — operating notes

Read readme.txt first. These notes describe existing behavior and limits.

== Renamed 1.0.9 installation and data migration ==

Back up first. For the old newsletter-platform slug, update to 1.0.8, deactivate old Free and Pro, then activate the renamed Free and complete Plugins > Newsletter data upgrade before installing matching Pro. Do not uninstall or reactivate the old pair. Already sent emails and saved content can reference images under the old plugin folder. Keep those static image assets available, or arrange exact old-to-new asset redirects with your host before removing the old files. The plugin does not rewrite previously delivered emails or configure web-server redirects. Existing multisite data requires a coordinated migration; automatic migration is refused.

Use an account with the standard WordPress Administrator role and permission to activate plugins. A custom newsletter role with added administrator capabilities cannot perform this migration because its role identifier changes between batches. After deactivating the old pair, let their running web requests and background jobs finish before continuing. Legacy migration requires MySQL 8.0 or MariaDB 10.6 or newer and InnoDB options, posts, user metadata and newsletter tables. Fresh installations do not require this migration. Very large or unrecognized legacy state needs a coordinated host review; do not clear a refusal by deleting records or resetting signing keys.

Migration runs in explicit, bounded administrator steps. Both old plugins must be inactive and background work must have finished. Busy jobs, conflicting destination records, nontransactional storage or uncertain ownership stop the migration. Do not remove old data or reset signing secrets to clear an error. The new plugin remains inert until migration finishes. A new installation needs no migration. After completion, review existing sending settings before restoring scheduled operation; matching Pro requires Free 1.0.9. Earlier Pure Elixirs installations require a separately verified migration.

Legacy public links and provider callback URLs use compatible validators. Previously saved signup blocks, shortcodes and merchant coupon metadata remain recognized. The new shortcode is [newsletterplatform_com_signup].

Current tracked links use independent random newsletter keys, and unsubscribe/preferences links use per-subscriber secrets. Existing version-2 signatures and saved version-1 verification receipts are preserved. Unrecorded tracked links issued before 0.1.0-beta.9 cannot be reconstructed safely and are refused; WordPress authentication salts are no longer used. Back up signing keys, receipts and mappings together.


If you installed the rejected pluginsshop-newsletter-platform 1.0.9 candidate, deactivate that Free and Pro pair and let their running jobs finish before activating newsletterplatform-com Free, followed by matching newsletterplatform-com-pro. Do not uninstall the previous pair: its uninstall option can delete shared data. The new pair reuses the NEWSPL data namespace, settings, signing keys and permissions without a second migration. Existing saved signup blocks, shortcodes, design exports, checkout consent metadata and issued public endpoints remain supported. Keep old static image URLs available for already delivered emails and saved image references. Never reactivate a previous copy alongside the renamed pair.

== Welcome sequences and replacement updates ==

Free includes ordinary multi-email signup welcome sequences. Start with one message or deliberately add, reorder and edit more, up to the shared 50-message operational bound. The active signup welcome receives new eligible confirmations only; imports and updates do not enroll old contacts. Only one signup welcome can be active at a time to avoid overlapping enrollment. A saved enrollment retains its own message snapshot; editing a workflow does not rewrite that history.

Existing legacy workflows and enrollment progress are retained. Eligible older ordinary welcome content can be reviewed and copied into a new Free draft explicitly; this does not modify the original, transfer its enrollments or resume held mail. Pause the old signup workflow before activating a replacement. Unknown conditions, commerce settings and required reviews cannot be removed by this copy action. Work needing a missing evaluator stays held. Replace Free first, then matching Pro without uninstalling.

The site frequency setting (24 hours by default) applies to broadcast campaigns. Automated sequences follow their authored delays, subject to sending windows, provider pacing and each subscriber's own frequency, topic and pause preferences. Changing this behavior does not reset existing settings.

== Health, review and reporting ==

Sending health reports observed worker checks and current queue holds; a completed check is not a delivery receipt. Pre-send review analyzes the saved revision for image alternatives, missing links and rendered HTML size. An optional workspace action checks up to three eligible public links per request using HEAD, without redirects. It checks at most 30 URLs per saved revision and needs cURL with direct public IPv4 networking. It excludes action, account, personalized and tracking links; unavailable checks do not mean broken links. This feature contacts the websites selected in the saved draft only when explicitly requested.

A completed campaign with no transport-accepted messages is shown as No acceptance recorded, without a sent timestamp. Failed or uncertain attempts retain their own failure/hold states. To try a corrected audience, duplicate the campaign and review the new draft before scheduling. Existing historical campaign statuses are not rewritten. For older unresolved campaigns whose receipts were already purged, the plugin cannot reconstruct acceptance that is no longer recorded.

Date-filtered reports use messages created within the selected site-local days and their current retained states. Associated click counts cover retained activity for those messages, not exclusively clicks within the chosen days. CSV exports the complete filtered result up to 1,000 campaign rows and asks for a narrower range above that limit. Contact activity combines retained consent events, message snapshots and enrollment snapshots; it is not a complete immutable audit log. Pro compares up to five selected campaigns and keeps matched-order currencies separate.


== Recovering an unconfirmed draft save ==

If the workspace shows Save not confirmed, the server may already have saved the draft even though its response was lost or incomplete. Further automatic and manual saves pause so the same action is not blindly repeated. Keep that tab open and use Export my draft before reloading or discarding edits. The JSON records the local email content and audience/review choices for recovery; it is not a complete site backup.

For a new draft whose server ID was not confirmed, Check saved campaigns opens the campaign list in another tab so you can inspect what reached the server while retaining the original local draft. For an existing campaign, Load server version replaces the local copy after confirmation; export first. The plugin does not automatically reconcile duplicate drafts or recover unsaved tab contents after a reload. Design import does not apply the exported audience or independent-review settings: recheck and deliberately reapply those choices before reviewing and scheduling a recovered campaign.


== Audience work and subscriber choices ==

Campaign rehearsal now runs in saved, resumable batches, with progress and cancellation. It uses an upper subscriber-ID boundary and checks the saved campaign revision again before marking the review complete. The result is an observation, not a frozen recipient list; consent, suppression, preferences and eligibility are checked again at delivery. Writers and reviewers can see counts without contact names or addresses. Saving a new draft invalidates an older review.

Invalid saved audience rule snapshots are rejected before saving. Older invalid campaigns pause without skipping their pending recipients or broadening their targeting. Choose Duplicate and explicitly confirm creating a repair draft without the invalid saved rules. This keeps the other saved filters but can widen the audience. Choose and rehearse the new audience before scheduling; cancel the old campaign when its pending work is no longer needed. Valid saved Pro rules still require their companion evaluator.

The workspace CSV preview and committed import use the same name limits: 100 complete UTF-8 characters per first/last name. Invalid database writes still roll back the entire batch.

CSV uploads support UTF-8 files up to 5 MiB, 20,000 records and 100 distinct columns. Map the columns, choose how existing contacts are handled, run the dry run, then explicitly confirm the import. Existing-contact updates change mapped profile fields only; they do not invent consent or reactivate suppressed contacts. Cancellation stops future batches and retains contacts already committed. Downloadable errors identify row numbers and reasons. Jobs belong to their initiating user, with at most five unfinished jobs per user. Imports process up to 100 records per batch; audience reviews process up to 50, with a short time budget. WordPress scheduled tasks and the open progress panel can advance work. Private CSV jobs expire after 24 hours and are removed when scheduled cleanup runs; completed or cancelled jobs clear the raw CSV immediately. Privacy erasure targets matching private work without deleting unrelated imports.

Administrators can define up to 20 custom topics plus General news. The signed preferences link in marketing messages lets an active subscriber choose topics, keep all topics including future ones, limit frequency to once a day, once a week or once every 30 days, pause for 7/30/90 days, or unsubscribe from all marketing. No selected topics means no marketing. Preferences never reactivate an unsubscribed contact and do not alter order receipts. Opening the link changes nothing; an explicit form submission saves the choice. Server-side checks enforce saved preferences before sending.


== Roles and sending protection ==

Writers can edit newsletter drafts; senders can also manage contacts, view reports and send; reviewers can inspect campaigns, view aggregate reports and decide independent reviews. Reviewers cannot edit content, send or view contact details. Settings and provider configuration remain administrator tasks. Server-side permissions apply even when an action is requested outside the interface. Roles do not grant access to unrelated WordPress administration.

Saved private templates and reusable sections are visible to their owner and site administrators. Only newsletter editors can create or delete their own saved designs; administrators can manage other owners' designs, including legacy ownerless designs. Generic WordPress Editor privileges do not grant access to these private records. Built-in designs remain available according to the installed edition.

Before sending confirmations or marketing, explicitly confirm the current production site identity in Settings. A changed home URL, site URL or non-production environment holds sending until reviewed. A clone with exactly the same URLs and environment cannot be detected by this check. Local tests and previews are still available. This is a sending guard, not a backup or migration system.


== Recovery and link preservation ==

For saved Pro commerce workflows, temporary or unverified WooCommerce history holds follow-up emails without advancing the journey. Those evaluations belong to the separately installed companion. Missing source orders need operator review; verified later purchases, refunded orders and recipient mismatches remain exclusions. Restored history lets an eligible saved step continue through normal consent and sending checks.

Link preservation stores opaque link/context identifiers and one-way signature commitments to keep previously issued URLs working. These records do not contain addresses or WordPress authentication secrets and do not generate analytics. They persist with authored destination mappings after personal reporting rows are erased; complete explicit uninstall removes them. Retain the dedicated signing keys in site backups. The plugin no longer derives or reconstructs signatures from WordPress authentication salts. See the 1.0.9 migration limits above.


The suppression key must be backed up with its matching newsletter database. If it is missing or corrupt while keyed history remains, operations that need it are held. Restore the original key from a backup that matches the retained database, then retry. Do not generate a replacement key or delete retained suppression records to clear the hold; those records protect previous opt-outs.


== Signup placement ==

Add the NewsletterPlatform.com signup block, or use:

[newsletterplatform_com_signup]

Optional shortcode attributes include title, description, button, source and show_name="no". Enable signup forms in Forms and complete sender setup before publishing. Test mode must be off to display a public form and accept signups. On the confirmed production site, enabled forms can send requested confirmation emails while campaign and automation sending remains paused. Turn forms off to stop new signup requests and confirmation sends. This does not enable marketing delivery. Consent is always a separate, unchecked choice.

Opening a confirmation or unsubscribe link displays a review page. A human confirmation POST changes the subscription. Mail providers can use the dedicated RFC 8058 one-click POST endpoint. Confirmation links expire; unsubscribe links remain usable after WordPress salt rotation.


== Sending and data ==

The plugin uses WordPress wp_mail() and the site's configured mail transport. A successful handoff means accepted by that transport; it does not prove inbox delivery. Free can optionally record basic newsletter link requests and show campaign/link summaries. The separate Pro companion adds journey breakdowns and conservatively matched WooCommerce orders. Free can optionally accept signed SendGrid SMTP event webhooks when a working SendGrid SMTP transport, HTTPS endpoint and valid public verification key are configured. Verified correlated hard bounces and spam complaints suppress future delivery; temporary blocks and unmatched events do not. Other providers are not integrated. Connector installation does not configure SMTP or establish that it works. No open pixels or invented engagement metrics are included.

Basic reporting is off by default and requires an explicit administrator setup acknowledgement; that acknowledgement is not subscriber consent. A contact can be excluded from measurement without changing their subscription. Click requests can include security scanners and forwarded messages; repeats within 60 seconds count once. No IP addresses, user-agent history, tracking cookies or open pixels are added. Personal reporting retention is 30–365 days, with WordPress privacy export/erasure. Free retains authored destination mappings so old links work after tracking is disabled or Pro is removed. Enabled basic campaign click reporting continues in Free; Pro order and journey features stop without the companion. Current tracked links use independent random newsletter keys, and unsubscribe/preferences links use per-subscriber secrets. Existing version-2 signatures and saved version-1 verification receipts are preserved. Unrecorded tracked links issued before 0.1.0-beta.9 cannot be reconstructed safely and are refused; WordPress authentication salts are no longer used. Back up signing keys, receipts and mappings together. Required-review campaigns remain blocked when Pro is unavailable. During a Free-first update, an incompatible older Pro companion is treated as unavailable until the matching companion is installed. Update Free first, then matching Pro without uninstalling either plugin. Ordinary Free campaigns do not require an independent reviewer.

Marketing workers use WordPress Cron, or Action Scheduler when available. Production scheduling needs a reliable host cron. Default pace is five attempts per batch, a maximum of thirty attempts per rolling hour, and a 09:00-19:00 window in the site timezone. An optional throughput profile, enabled only after the owner acknowledges their provider allowance, supports configured limits up to 6,000 attempts per hour and 100 per pass, with a one-minute scheduled cadence. The effective hourly limit also respects the owner-declared provider cap. Each worker stops starting more deliveries after a 20-second budget; an in-flight mail transport can take longer. These are control limits, not a promised send rate. Host cron, SMTP latency and provider limits still determine actual throughput. Frequency limits are checked again before sending. An interrupted attempt can be marked unknown and requires operator review; exactly-once delivery is not claimed. Reports provides a separate paged list of failed and uncertain messages, oldest first. Retry applies to the selected saved message and rechecks current permission and approval. Already accepted recipients are not repeated. Held Pro campaigns cannot block unrelated campaign preparation.

Subscriber records, consent history, drafts and delivery metadata are stored in this site's database. WordPress privacy export and erasure integrations are included. Erasure retains a keyed suppression marker to prevent accidental reimport. Form dismissal uses browser-tab session storage and signup completion uses a functional cookie. Operational event retention is configurable. Sent, cancelled and skipped queue entries and their attempt records are removed by scheduled cleanup once their last update is more than 90 days old. Campaign receipts remain while their parent campaign is unresolved, so delayed finalization cannot lose evidence of an accepted message. Other unresolved work remains available for review. Suppressions and consent are retained separately. Removing the plugin retains data unless Delete on uninstall was explicitly selected. Historical WooCommerce coupons are retained as merchant records on uninstall. SendGrid correlation records and event receipts have 90-day retention with bounded scheduled cleanup. Verified provider suppression fingerprints remain until explicit plugin-data deletion, including when feedback is disabled. Privacy erasure removes contact-linked correlation/event data and retains suppression protection.


