lanxalot

Hi?@amimulihsanmahdi

I finally found time to swicth the SMTP solution to Amazon AWS and Fluent Forms + Fluent Forms SMTP. Everything works fine. It seems there is a compatibilty issue with the Zoho SMTP setup/ plugin. I also believe the fault is with Zoho’s methods.

Many thanks for your help!

Hi @amimulihsanmahdi

Thank you for the reply! Sorry for the delay in my response, I will switch the DNS service and see if it works. I will let you know ASAP.

Many thanks!

Hi Amimul,

Many thanks for the reply. On this site I am using the Zoho Mail plugin for SMTP as the client is using Zoho mail. Do you know if this is compatible with Fluent Forms?

Many thanks for your help!

Same

Mine too. Perhaps you meant one star? 5 = good. Cheers

Hi, thanks for your reply.

The screenshot shows that the ‘Required Field’ is unticked as this is a current work around we have to allow the form to be sent. As soon we we make the field compulsory, the form won’t send anymore. It’s a very simple Text Area field with no conditional logic or any other parameters other than it should be compulsory for visitors to complete.

Flexible Checkout Fields Version 4.1.3

Woocommerce: Version 8.6.1

WordPress Version 6.4.3

PHP V 8.0

Thanks for looking into this.

@ramwoodstudio

Check option three in the solutions I posted above. Will only take you a moment to test. Cheers!

Hi @nanny7

For some settings, you need to synchronise the orders (in the same advanced tab/ window) before you can change them.

Many thanks?@sureshramasamy!

Option 3 below has done the trick for me. It’s an easy setting to change, no need for a roll back. I have no need to enable the option anyway, surely it should be disabled by default?

What action should I take?

• Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
• Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
• If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.

• This reply was modified 9 months, 1 week ago by lanxalot.

Thanks @sureshramasamy

For those still having issues, try option 3 below, it’s a quick and easy setting to test:

What action should I take?

• Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
• Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
• If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.

Try option 3 below (it’s an easy setting to apply and test):

What action should I take?

• Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
• Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
• If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.

What action should I take?

• Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
• Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
• If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.

Many thanks @sureshramasamy many thanks!

Option 3 below has done the trick for me. I have no need to enable the option anyway, surely it should be disabled by default?

What action should I take?

• Plesk already has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
• Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
• If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.

HI Steve @thewebsmiths,

That’s interesting, I just disabled Modsec to test on 8.51 and still got the error.

I’m also still getting the critical error after the new update. There seems to be an issue with the 2 most recent Woocommerce updates.