Minor Release: FluentCRM 3.1.5
A minor one today, focused on improvements and performance.
FluentCart checkout subscriptions
You can now turn FluentCart customers into subscribers right at checkout. Under Settings → General Settings, there's a new FluentCart Checkout Subscription section. Enable it and a subscription checkbox shows up on checkout, above the payment methods. You control the label, target list, tags, default state, and double opt-in. When the order completes, FluentCRM creates or updates the contact automatically.
More reliable campaign sending
We improved how campaign queues are processed. It now handles multiple queue runners more safely, recovers stalled emails more reliably, adds fallback mechanisms to keep campaigns moving, and fixes a chunking issue that could skip recipients on large sends.
Smaller wins from the community
- Global link color option in the Gutenberg email editor.
- Quick company creation, right from the contact selector.
- Clearer campaign progress for large sends.
- CSV export for system logs, with date range filtering.
- SmartCode links in the editor work properly again.
Plus better CSP compatibility and a long list of fixes across the email editor, revenue reporting (HPOS support for WooCommerce), and automations.
Full release notes: https://fluentcrm.com/blog/fluentcrm-3-1-5/
A lot of this came from conversations here. Thank you. Update when you're ready 🚀
Speaking of double opt-in, have you considered adding double opt-in on a per list basis (required for GDPR compliance)? The only fix needed is to:
- Send out the double opt-in mail to existing contacts before they’re added to an additional list, unless they’re logged in, of course.
- Store how the changes were made (manually by admin, by double opt-in, already logged in).
Karl Emil Nikka As explained previously: Lists are just taxonomies like tags so our whole architecture does not treat contact status as lists/tags based and I think all the email marketing solutions works like that. Many call lists / tags as Segment / audiences.
So if you are treating Lists as separate entity then that's not how we designed it. So I would not say, it's a breaking feature for GDPR. if a customer subscribe then it's a global subscription and it's the same as unsubscribe mechanism.
Shahjahan Jewel Let me put it another way (regardless of how lists are intended to work). Here’s how it actually works using the default subscription form: any visitor can add additional lists to any existing subscriber. We’re not allowed to let one user affect another users subscription settings. That’s why we need double opt-in for all lists, unless the contact is an authenticated user subscribing to additional lists.
Karl Emil Nikka Adding to a list should be from the source, right? A list can be added in different way, so if you are using a form for public users, the form should handle the double optin before processing the data (FluentForms has it btw). If you are an admin and importing contacts and adding to a list/tag, that's verified by the admin.
Again, list/tag is just data attributes that you choose to add/remove from a contact by different ways. It does not have any relationship with your contact status.
Shahjahan Jewel Yes, it’s possible to solve using FluentForms Pro (and we use a competing form plugin to do the same). I just wish it was built in into FluentCRM, especially since you’ve already added list-specific double opt-in emails.
Shahjahan Jewel Addition: or just add a small disclaimer about the need for FluentForms Pro on sites with more than one list. I’m not bothering you about this for our own use case since we’ve already solved it. I’m doing it because I want to promote FluentCRM among privacy focused organizations.
Shahjahan Jewel It would also be great if we, for a consistent design, could design the double opt-in emails with the new excellent email builder. Please consider adding it to your internal feature request board.
Shahjahan Jewel Regarding your comment ”a list can be added in different way, so if you are using a form for public users, the form should handle the double optin before processing the data”. Even FluentPlayer lacks proper double opt-in support. Don’t you think it would be better to fix the underlying issue in FluentCRM than add a custom double opt-in support to every other plugin, including your own?
Shahjahan Jewel The global link is a super great addition, but I noticed we can't set up the hover ?
Élyse Bergeron CSS in email is very complicated and we can't push all the css as we do for web.
Shahjahan Jewel But it is available in the paragraph block though ?
Élyse Bergeron Yes, I will check how we can add it globally as well.
Shahjahan Jewel Thanks this is such a great improvement.
Thank you so much for adding compatibility with secure CSPs!
Love it!
Thank you for the FluentCart checkout subscription 👍
It keeps getting better day after day
Shahjahan Jewel Thank you for the checkout subscription !!! Will it be possible to add it to the modal checkout ?
Are there any plans for adding support for a custom unsubscribe page (like the custom subscription management page introduced in FluentCRM 3.0)?