Aplose Newsletter
| 开发者 | oandrade |
|---|---|
| 更新时间 | 2026年11月4日 00:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Visitors submit first name (optional), last name (optional) and email (required), plus consent.
- WordPress stores a pending subscription and sends a confirmation email via
wp_mail. - The confirmation link opens a page with a confirm button (a simple GET never confirms).
- After confirmation, the contact is created or found in Mautic and added to the selected segment.
- Display modes: shortcode
[aplose_newsletter]and optional site-wide exit-intent popup. - Mautic connection via OAuth2 (authorization code). Client secret and tokens stay server-side and are never sent to the browser.
- Optional admin notification email when someone confirms.
- In-plugin documentation under Aplose Newsletter → Documentation.
fr_FR) are included. The site language in Settings → General controls which translation is used.
Try it: subscribe to the Aplose newsletter on https://www.aplose.fr/ (powered by this plugin). Welcome bonus: a 6-step method to create and run your business, with concrete examples.
MGC Premium: WordPress and Mautic are provided on the Ma Gestion Cloud MGC Premium plan (dedicated managed hosting, no extra software licence).
Caching note: if full-page caching is enabled, exclude pages that display the newsletter form so the REST nonce stays valid.
安装:
- Upload the plugin folder to
/wp-content/plugins/or install through the WordPress Plugins screen. - Activate the plugin.
- Go to Aplose Newsletter → Settings.
- Create an OAuth2 API credential in Mautic using the Redirect URI shown in settings.
- Enter your Mautic URL, Client ID and Client Secret, then click Connect to Mautic.
- Select the target segment and save.
- Enable the shortcode and/or exit popup as needed.
- Place
[aplose_newsletter]on any page, post or widget.
常见问题:
Where does the plugin send data?
Confirmation emails are sent by WordPress (wp_mail). After the visitor confirms, WordPress calls the Mautic REST API at the base URL you configured, using OAuth2 tokens stored on the server. Catalog/marketing traffic goes only to that Mautic instance — not to the plugin author's servers.
Who sends the confirmation email?
WordPress, using wp_mail. The Mautic contact is created only after the visitor confirms.
What redirect URI should I use in Mautic?
Copy the Redirect URI from Aplose Newsletter → Settings. It looks like:
https://your-site.example/wp-admin/admin.php?page=aplose-newsletter&aplose_newsletter_oauth=1
Are OAuth secrets exposed to visitors?
No. The client secret and access/refresh tokens stay in WordPress options on the server. Front-end JavaScript only receives the REST URL and a WordPress REST nonce.
Can I close a browser tab and show the popup?
No. Browsers do not allow custom UI on tab close. The exit popup uses mouse leave at the top of the viewport instead.
Why do scripts load on many pages when the exit popup is enabled?
When the exit-intent popup is enabled, CSS/JS load site-wide so the popup can appear from any page. If you only use the shortcode, disable the popup and assets load only when the shortcode is rendered.
What happens when the Mautic OAuth token expires?
Access tokens are short-lived (often about one hour). The plugin refreshes them automatically: on API calls, and twice a day via a WordPress cron job so the session stays alive even if nobody opens the admin or confirms a signup. Each successful refresh stores the new refresh token when Mautic returns one.
If the refresh token itself expires (for example after many days of inactivity longer than your Mautic api_oauth2_refresh_token_lifetime), automatic refresh is no longer possible. The plugin then marks OAuth as degraded, shows an admin notice, and emails the notification address (or admin_email) at most once per 24 hours. You must click Connect to Mautic again. The cron prevents this in normal use; it cannot reconnect without a human once the refresh token is dead.
Recommended Mautic OAuth lifetimes?
For hosted instances, prefer a refresh token lifetime of at least 30 days when you can configure it. The plugin cron (twice daily) keeps the session warm within whatever lifetime your Mautic instance allows.
更新日志:
- Proactive Mautic OAuth refresh via twice-daily cron; health flag, admin notice and throttled alert email when refresh fails.
- Keep “Tested up to” only in readme.txt (WordPress.org plugin header rule).
- Complete French translation pack (en/fr), refreshed POT, and robust textdomain loading for WordPress.org language packs.
- Documentation: live demo CTA (Aplose newsletter + welcome bonus), stronger Mautic positioning, MGC Premium includes Mautic and WordPress.
- Align readme with WordPress.org review model (External services, data-flow FAQ); no Angular front-end in this plugin.
- Plugin Check compliance: i18n translators comment, Tested up to, sanitization, prefixed uninstall vars, DB phpcs notes.
- Optional admin notification email when a visitor confirms their newsletter subscription.
- Admin screen to list pending and confirmed subscriptions, with row and bulk delete.
- When an already confirmed email is submitted again, send a status email while keeping the same on-screen success message.
- Refresh confirmation screens after clicking the email link (icons, card layout, styled buttons).
- Clickable privacy policy link opens a configurable popup from settings.
- Refresh public form visuals: mail icon, styled subscribe button, clearer layout.
- Fix OAuth authorize URL encoding so redirect_uri with query args matches Mautic.
- Switch Mautic authentication to OAuth2 (authorization code). Redirect URI shown in settings.
- Added admin documentation (how it works + Aplose Ma Gestion Cloud / MGC Premium).
- Initial release: double opt-in, Mautic sync, shortcode and exit-intent popup.