FluentCRM 3.0 - RC.1 is available

Ric Valenzuela 

Ric Valenzuela 

Ric Valenzuela 

Ric Valenzuela lol! Thanks. Crazy day!

Ric Valenzuela I came here to post the same. 😆

Ric Valenzuela I'm going to use that phrase though, aren't you? I liked it.

Ramsis Kasis Thanks for reporting these important bugs. I hope the team can address them before the release.

JF Thanks I've opened a support ticket with full details , hoping the team can address these before the stable release. The Global Styles and Tag-applied trigger issues in particular aren't RTL-specific and affect every user.

Ramsis Kasis Template import and automations are working as confirmed. RTL and Editor issues are being addressed.

Masiur Rahman Siddiki perfect

Cointacter Release Candidate

Parm Saggu #littelthings make #bigthings Probably moreover on this one, this is a big deal to any business who is serious about running a CRM. Big deal! I often imagine myself as Shahjahan Jewel and just think about how big this business could be if all the important #littlethings were a priority. It's a crazy opportunity. Crazy!

Parm Saggu We made the contact export super fast. Give a try with this new version.

Shahjahan Jewel I'm in the middle of a launch, I'm worried that changing my tech now might cause issues, I was waiting for the official release!

Karl Emil Nikka 

• We have added custom preference page now via shortcode and users will be redirect to that page. Will take a look about the unsubscribe page as well.
• Removal of all unsafe-inline scripts => Would you please give me more details about it? We don't load any scripts on frontend.
• FluentCRM's core subscription is contact level not list level.

Shahjahan Jewel Thank you for the reply and for looking into the unsubscribe page. FluentCRM enqueues inline-scripts (without nonces) on the settings pages and the email browser view. See ticket 102205 for details.

Even though the core subscription is on the contact level, it would be great (necessary for GDPR compliance) if we could have the an option on the list level to require double opt-in before it’s added to the already subscribed contact. It would work almost the same regardless of whether the contact is subscribed or not. If subscribed, use the opt-in email as a condition before adding the list to the contact. If not subscribed, run through the regular process.

Shahjahan Jewel Just let me know if you need any additional information.

Shahjahan Jewel "FluentCRM's core subscription is contact level not list level." If you could address this, I'd really appreciate it. ITM, one can always unsubscribe from a any list or tag via a smartlink. Their only needs to be a way to email/list-level customize the footer, which usually holds the unsubscribe link.

And... there needs to be a preferences page where the customer can see what lists / tags he's on, and why, and also allow him to remove himself from any given list / tag - with the obvious consequences. It's almost like a cookie manager. Tell me what you do with "me", and allow "me" to say yes or no to it.

Anyone else echoing this sentiment?

Shahjahan Jewel "FluentCRM's core subscription is contact level not list level." Sadly this is a serious restriction. In order to meet the framework of existing laws and conventions, there would need to be changes to this.
At L1, an email needs to be validated for a 'master' subscription; and if eg. bounced, that should be removed in order to invalidate all further subscriptions. This is the level I see your 'core' subscription status.
On L2, GDPR consent to marketing should allow subscriptions to any marketing lists. But this should NOT prevent transactional emails on non-marketing lists
And on L3, subscription by list, subject to L1 & L2, should be easy and List Unsubscribe should operate on L3, Ideally it would also clearly offer withdrawal of L2 GDPR.

Helmar Rudolph Yes, I agree. It’s important that the subscription management page can be configurable. The contacts should only be able to select between a defined set of lists (not all lists). The contacts should also not able to change tags if we don’t allow them, since the tags might be used for administrative purposes. The contacts should however be able to see and export all data we’ve collected about them, including assigned tags (not unassigned tags).

Christopher Miller Great suggestions. I know we’re already at release candidate status, but I’d love to see a future ”FluentCRM 3.1” release being announced as a fully GDPR compliant version of WordPress’ best email marketing plugin, Shahjahan Jewel .

Karl Emil Nikka, If you say GDPR status depends on the Lists subscription, then we have a very different understanding of the system. As I said before, Lists are the same as Tags. Lists are available just to let you categorize your contacts more granular way. If you want to use that as a mailing list you can definitely use that, and in that case, you have to manage your own confirmation and maybe use smartlink for removing from a particular list.

When you send a campaign, you are not required to select a list. You can send to all the contacts, a particular tag, or a subset of a list.

Christopher Miller 100%

Shahjahan Jewel it's not so much about the understanding of the system, but real-world application and requirements. Maybe the cookie analogy is the best. There are required lists and tags that are essentially read-only and maybe not even exposed to the customer. Then there are optional lists and tags that the customer should be able to remove himself from without a site-level unsubscribe.

Karl Emil outlined that nicely.

Shahjahan Jewel The GDPR is very clear: we must to protect the integrity of a contact’s settings. We may not let Contact A control Contact B’s settings. The way FluentCRM works today is not compliant since Contact A can sign up (existing) Contact B for additional lists.

Karl Emil Nikka This is an interesting and valid point. However there are multiple ways to add Contact B to additional lists, and not all are vulnerable to this in practical terms. For example, someone clicking on a link in a previous email's manage subscription page or logged-in user could be assumed to have confirmed identity as Contact B, whereas a public form to subscribe to a different newsletter could arguably need such confirmation by double opt in. However for already known emails, this is obviously a low risk which could be managed by a documented decision to balance the interests of the contact by reducing steps required, or an automated notification when adding to any list, rather than an additional GDPR consent opt in.

Shahjahan Jewel For me, by far the most important change would be mapping List Unsubscribe to a list, not global subscription status. I have some ideas on how this could be achieved easily. Happy to discuss.

Christopher Miller it would already help to replace the global unsubscribe link in the footer with one that removes the contact from the list/tag that triggered the email. A redirect to a page notifying the contact of the nature of the unsubscribe would round it off.

There should be a protection against 3rd party unsubscribes though, so that no one can unsub you because maybe you forwarded the email to them.

Helmar Rudolph That would help, but there are already workarounds. The list unsubscribe has no possible workaround. Really the workflow needs to have list selection at the point of setting up the campaign.

Christopher Miller Yes. I built our current Gravity Forms based subscription management system with that in mind. Every list has double opt-in except when the contact is a logged in user.

Shahjahan Jewel I saw that Christopher Miller already has offered to discuss solutions, but if you want my input as well, you’re more than welcome to reach out to me on e.g., Signal (karlemilnikka.24).

Has anyone in this thread heard any news regarding the concerns we raised, Helmar Rudolph and Christopher Miller?

Karl Emil Nikka No. I'm still cautious about updating until I can devote some time to fixing anything necessary.

Christopher Miller I see. Shahjahan Jewel, just let us know if you need any additional information.

Idan Nagar You tried with twillio or aws ?

Masiur Rahman Siddiki i even cant choose one of them, i see errors. I already opened a ticket about it and its still not solved, who can help urgently? Itsore than 1 month like that

Idan Nagar Can you tell me the ticket number please ?

Masiur Rahman Siddiki 155471 thank you

Camilo Barrett we will try to ship with version 3

Shahjahan Jewel 

I'm getting the same issue with RC1.

michael padilla what error are you getting?

Zsolt Lázár What do the stats say where the flow goes (yes vs no), and what is your condition?

Victor Drover Same problem here with RC1 Shahjahan Jewel can you check this issue ? half of our pages have missing contents (synced patterns) with RC1 (theme : TwentyTwentyfive)

Nicolas D I'm using this snippett until it's fixed:

add_action('init', function () {if (!class_exists('\FluentCrm\App\Services\BlockParser')) {return;}

global $wp_filter;

if (empty($wp_filter['render_block']) || !is_a($wp_filter['render_block'], 'WP_Hook')) {
    return;
}

foreach ($wp_filter['render_block']->callbacks as $priority => $callbacks) {
    foreach ($callbacks as $id => $callback) {
        $fn = $callback['function'] ?? null;

        if (
            is_array($fn) &&
            is_object($fn[0]) &&
            get_class($fn[0]) === 'FluentCrm\App\Services\BlockParser' &&
            ($fn[1] ?? '') === 'alterBlockContent'
        ) {
            remove_filter('render_block', $fn, $priority);
        }
    }
}

}, 999);

Victor Drover Thank you :)

Victor Drover The issue has been resolved in dev branch. Releasing new RC today.

Jason Janes That's a pertinent question. My FluentCRM review is from 2021 and it's time for a revision focusing on the new release. I just updated my FluentCart review and it's even outranking the WP Manage Ninjs review, so daddy gots to shoot for another win with this rewrite.

Bernhard Smith Feel free to add here. I am checking this reported issue now.

Bernhard Smith Just to let you know, we have fixed the issue already. We will release a new RC in a few hours.

Shahjahan Jewel i think it was the same problem than this one

Nicolas D yes, this issue actually already solved in our dev branch. We'll release an update later today.

Shahjahan Jewel Great thank you !

Bernhard Smith I will take a look. Thanks for the feedback again.