NewsLetter Documentation
This reference describes the local distribution 1.2.1 controls and the recommended configuration order. It is not a substitute for checking the shipping environment.
Installation and migration
- Back up files and database; test restoration in staging.
- Check the requirements and disable the three original plugins Automated, Fluent Forms and AI before activating the merged package.
- Upload the plugin ZIP from Plugins → Add new and activate it. The Newsletter core is included; you don’t need another kernel installation to get started.
- If you maintain a supported external Newsletter, check that it is reused and that there is no loading conflict.
- Open Newsletter and fill in the sender identity, lists, and mail provider.
Automation channels
In Newsletter → Automated select template, posts, categories, lists and frequency. Assign an account with appropriate permissions to generate the content. Preview the newsletter and send an internal test before enabling the channel.
Integration with Fluent Forms
Install and activate Fluent Forms if you need this source of subscribers. In its integration Newsletter maps the email, name and lists. Define the consent field and confirmation policy according to the treatment of your site. Try a controlled address and check both subscription and unsubscription.
Artificial Intelligence Consents
Under Settings → Newsletter Automated Artificial there are two separate controls: IA Provider Authorization set to WordPress for Composer Features and Service Authorization Newsletter. The latter transmits text, title, description, domain and license to api.thenewsletterplugin.com. Requires valid license from provider; Do not enter sensitive data and review the result before sending it.
Late cron and logs
- Default policy: Drop schedule if cron arrives on another day.
- Optional recovery: age between 1 and 72 hours, 24 by default; up to three attempts per operation.
- Valid reservations prevent concurrent executions of the same channel.
- Records retention between 7 and 365 days, 30 by default; cleaning operates in batches.
Set the time zone of WordPress. If you use a server cron, verify that it calls the WordPress mechanism and avoid overlapping schedules.
Signed Updates
Configures the publisher’s Ed25519 public key received over a trusted channel. The updater checks the HTTPS manifest, signature, SHA-256 hash, and ZIP structure. Do not enter a private key. The existence of the verifier does not guarantee that an update is published.
Initial verification
- Review dependency diagnostics, cron, AI, and updates.
- Checks confirmation, deregistration and a delivery to the internal list.
- Verify that deactivating the package stops its scheduled tasks from running.