lanxalot
Forum Replies Created
-
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.
Forum: Plugins
In reply to: [WooCommerce] Update today and website in critical errorCheck option three in the solutions I posted above. Will only take you a moment to test. Cheers!
Forum: Plugins
In reply to: [WooCommerce] Update today and website in critical errorHi @nanny7
For some settings, you need to synchronise the orders (in the same advanced tab/ window) before you can change them.
Forum: Plugins
In reply to: [WooCommerce] Update today and website in critical errorMany 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 218500being 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 2 years, 2 months ago by lanxalot.
Forum: Plugins
In reply to: [WooCommerce] Major Critical Errors with Woo 8.5.1. Why the lack of response?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 218500being 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.
Forum: Plugins
In reply to: [WooCommerce] New update 8.5.1 still errorsTry 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 218500being 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.
Forum: Plugins
In reply to: [WooCommerce] Frequent 404 error on single product and product category pageWhat action should I take?
- Plesk already has a help article targeting this issue, identifying Comodo rule with
ID 218500being 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.
Forum: Plugins
In reply to: [WooCommerce] More Major Critical Errors with Woo 8.5.1 and 8.5.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 218500being 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.
Forum: Plugins
In reply to: [WooCommerce] Major Critical Errors with Woo 8.5.1. Why the lack of response?HI Steve @thewebsmiths,
That’s interesting, I just disabled Modsec to test on 8.51 and still got the error.
Forum: Plugins
In reply to: [WooCommerce] woocommerce causes Critical ErrorI’m also still getting the critical error after the new update. There seems to be an issue with the 2 most recent Woocommerce updates.
Forum: Plugins
In reply to: [WooCommerce] woocommerce causes Critical ErrorTry downloading the plugin from this page, and then simply upload and overwrite the existing. Back up first of course.
We just had the same on a site, and it showed Woo was up to version 8.5.0
This also shows on other updates. The latest version on here is 8.4.0
The odd thing is, after ‘downgrading’ to 8.4.0, there is no update to run.
Something strange must have happened with the updates?
Hopefully this will fix the issue for you too.
Ok, thanks for your time. I’ll test for conflicts.
Hi again,
Unfortunately the sound has stopped working again. I made no changes to the code or any other but after approximately 48 hours, no sound plays on the site. Even if you visit the homepage from a link within the website. Before, the sound only played when you visited the homepage from a link or click on the website, but not from landing there from a search engine. Now there is no sound at all. I also tried getting the sound to autoplay on a different page of the site, but nothing. Just silence.
Do you have any idea why this might have happened and any suggestions for a fix?
Many thanks
Thank you. That is working now 🙂 Great stuff!!!
- Plesk already has a help article targeting this issue, identifying Comodo rule with