Jainil Nagar

If you are not receiving email notifications from your forms, this usually related to how emails are being sent from your site rather than the form plugin itself.

Here are few things you can check:

1. Mail settings in Contact Form 7:
   Make sure the “To” email address is correct and properly formatted. Also, check the “From” address as it is recommended to use an email that matches your domain
2. Check Spam/Junk Folder:
   Sometimes emails are delivered but they end up in the spam.
3. Test WordPress Mails:
   Try using another plugin or test feature like password reset to see if the emails are working at all. if not, the issue is likely with your server/email configuration.
4. Use SMTP instead of PHP mail:
   Many hosting providers block or limit the use of PHP mail. Using SMTP to send email via a proper mail server like Gmail, Outlook, etc.
5. Try and Check Email Logs:
   Try an email log plugin to see if the emails are being logged or not, and if your hosting provider provides Email logs, and then check there as well.
6. Check hosting restrictions:
   Some hosts requires specific email configurations or block outgoing mail by default.

It may help if you share your mail tab configurations, any error messages you see or environment information.

The cause of the error should be found in the error log, which is accessible in your hosting panel. If needed, your hosting support can assist you with this.

Another option is to enable debugging in WordPress. Instructions for this can be found here: https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/

Since the error is occurring on the Themes page, it’s likely related to a theme or plugin conflict, but the exact cause will be clearer once you check the logs.

• This reply was modified 1 month, 1 week ago by Jainil Nagar.
• This reply was modified 1 month, 1 week ago by Jainil Nagar.

That email is triggered when WordPress detects a PHP fatal error, so in your case there was a fatal error at some point.

Not all fatal errors are major in terms of impact. Even something as small as a typo, like a syntax error, can cause a fatal error in PHP, which will stop the script from executing and trigger that notification.

The plugin support confirmed that they have identified the issue and it is a minor issue then should not have any major impact on your site and they will resolve it and release a new update.

I believe you’re trying to add a price modifier per attribute term (e.g., XL → +₹100), which isn’t supported by WooCommerce core.

In WooCommerce, attributes and their terms don’t have pricing logic by default and pricing is only handled at the variation level.

For cases like yours, where multiple attributes can lead to many combinations, a common approach is to use a product add-ons/extra options extension. These allow you to define options like Size or Color and assign an additional price to each selection, which is then added to the base product price dynamically on the frontend.

For example, WooCommerce’s own Product Add-Ons for WooCommerce extension is one option that provides this functionality, and there are also similar plugins available depending on your needs.

This might be due to the conditional fields plugin. Please check this Support Thread.

• This reply was modified 2 years, 6 months ago by Jainil Nagar.

https://mfaeca.org/wp-json still shows the restriction.

Yes, but it is only enabled for the logged in users. CF7 uses the rest api. So when the guest user submits the form the submission does not work.