Shahjahan Jewel

@codersajjad, Your issue was with a pro version feature and I am not sure why you did not submit a support ticket on our customer portal instead you posted here. The WP repository support is only for free version’s users and it’s related features.

Also it’s really not fair that you rated 1* for a miscommunication. I would still recommend submitting a support ticket for any premium plugin-related issues.

Thanks

For all the premium feature related issues please open support ticket here: https://wpmanageninja.com/support-tickets/

Hello @codersajjad, We reply every ticket within 24 hours on weekdays. Would you please please let me know your ticket ID so I can take a look.

Thanks

Dear @dominiks8318, Thanks for your feedback. Most of the features in Fluent Forms are totally free including all the basic fields, submission storage, emails etc. And I think Fluent Forms is the very few plugins where all these features are 100% free.

As we use a freemium model to support the development of this plugin, we have to make certain features premium, and File Upload is one of them. I am not sure how File Upload is a basic field as far as I know all the form plugins make the file upload a premium feature.

Again, thank you for your feedback and I hope you reconsider to revise your review based on other features Fluent Forms Provide.

Hello @mobizma,

As we stated, we encrypt the SMTP credentials and use the salts as key for this encryption / decryption. Plugins should not store the SMTP credentials directly to the database.

I am not sure why you ever need to regenerate the salts unless you get hacked. There is a very good technical article about it here. Please read: https://snicco.io/blog/wordpress-salts

About the 2nd part of your question: Yes, we only allow one SMTP credential for each driver to store in wp-config.php and that is by design.

If someone unsubscribe then they will be excluded automatically from next campaign emails.

I have replied to your ticket with solution.

Thanks

@internetzer22, would you please try now. It should work now.

We have fixed the issue in version 2.8.42

Thanks

Most likely it’s Litespeed’s ESI caching which cached the REST request. In the latest version (2.8.42) we have improved the compatibility with Litespeed. So please update and it should be resolved. Also if you see this message in normal way that means the rest api token got invalid and you can just reload the page.

Thanks

No, pro version does not require an update for this one. The current pro version number is: 2.8.40

Latest post block is available in the pro version. Are you using the pro version?

We have fixed the issue in the lastest version.

The issue has been fixed in the lastest version (2.8.41)

Just released 2.8.41 which will resolve this issue.