URGENT: FluentCRM Update Required from 2.9.85 to 2.9.86
We had an issue with automation tracking in the FluentCRM 2.9.85 (yesterday's update).
Please update to 2.9.86 (Free core version only).
The issue: We had a database query misconfiguration in yesterday's update, which created draft automation entries in the database.
Please note, this bug did not interrupt your automations. It was related to logging and reporting.
We strongly advise updating to the latest version (Core: 2.9.86)
Hi Shahjahan Jewel , thak you for the heads-up but there is also a bug in the pro version of the plugin that I reported more than 2 months ago and that is still not fixed, with no commitment to fix it (although I was told that the issue was identified and should be resolved in 2.9.84). Versions after V2.9.31 of the pro plugin broke something and it hasn't been fixed since. Please see ticket #139515 (The posts block in FluentCRM doesn't show each post featured image on iPhone and on MS Outlook 2019/2021/2024 on PC). Please could you kindly take a look and get this fixed ASAP? It was working fine until 2.9.31, so we are stuck with 2.9.31. Thanks!
Screenplay Unlimited I discussed the ticket with our team. The problem is, we don't have any control over the email inbox content. So Outloook may block images from loading and they decided which images will be shown or not.
Screenplay Unlimited By the way, old email clients does not show webp sometimes.
Shahjahan Jewel Thanks, but that does make sense for two reasons: 1) it used to work fine until V2.9.30, and it still works fine with 2.9.31, so versions of the pro plugin after 2.9.31 have clearly broken something. That's why we are stuck with 2.9.31. 2) This doesn't only happen with old versions of MS Outlook, it also happens with the latest version of iOS on iPhone and iPad. That's why I'm bringing this to your attention, your devs are clearly missing something. Thanks for taking another look.
Screenplay Unlimited Nothing actually changed in our email renderer and composer between these two versions. But I will check with the team again.
Shahjahan Jewel Thanks for looking at my detailed report in the ticket. Something is broken after V2.9.31 and in all versions since, otherwise reverting to 2.9.31 wouldn't resolve the issue.
Shahjahan Jewel EDIT: I've corrected this and earlier posts, the last working version of the Pro plugin here is V2.9.31. However, with later versions, the problem I had with iOS 18.x clients (no featured image when using the latest posts block) seems to be resolved with iOS 26.1. The issue with MS Outlook 2019 and 2021 is also present with Outlook 2024 LTSC, so it's not only with older versions of Outlook. I'll update the ticket and we can continue the discussion there if you want.
Cool thanks for your proactiveness, I hope you introduce more checks and test cases prior to any release, it can help save us a lot of time...
Cheers Manoj
The free version does not show an update available. I only realized this after Solid Security flagged it as vulnerable. Came here to see if there was any additional info - and of course you guys are on it! 💪
I will install manually, but just wanted to share this issue. Same thing happened with the last update of Fluent Support. See this thread: https://community.wpmanageninja.com/portal/space/fluent_support/post/plugin-update-required-but-no-update-av
If others aren't having this issue, it's a conflict on my site somewhere...any idea where to look?
I noticed today when I set up a new automation that is triggered when a contact is subscribed to a tag that it doesn't get added to the automation. I updated everything to the current versions but this seems critical.
It works if I add it as a goal in that automation, but that shouldn't be necessary.
I guess I just realized that if the automation doesn't have any other steps in it, which it didn't have for the testing purpose that I did, nobody's added, but as soon as I added a wait step, for example, it seems to work now. So I guess that's supposed to be like that.
Christian Dian You need at least one action inside the automation. Otherwise it will not run as no action is required.