buzzingbee
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Form not working after 4.4.1 wordpress updateThe From: field is definitely meant to be an email address.
Yes. Well noted.
using
[your-name] <[your-email]>
is risky and will cause problems on many hosts.I’ve updated the From field to
Our Website Name <[email protected]>
. This works and allows the sales team to easily identify inbound email from the website.This Contact Form 7 Email Issues is an excellent post by the way. Also, I took a look at your cf7 skins. Very nice!
Forum: Plugins
In reply to: [Contact Form 7] Contact form 7 stopped working@buzztone Ok I’ll take a look.
Forum: Plugins
In reply to: [Contact Form 7] Customise SEND buttonYou could add the custom css into your child theme‘s stylesheet. For some themes, you can add custom css through the theme options. There are also some plugins for adding custom css.
Here’s an article that might help:
https://www.wpbeginner.com/wp-tutorials/how-to-style-contact-form-7-in-wordpress/Forum: Plugins
In reply to: [Contact Form 7] Contact 7 Form Stopped WorkingPlease note that some users may have issues with the default [your-name]<[your-email]> in the From field.
This is pointed out in buzztone’s Contact Form 7 Email Issues.
Forum: Plugins
In reply to: [Contact Form 7] Contact 7 Form Stopped WorkingWe had our website name in the From field. Using the default [your-name]<[your-email]> in the From field worked for us.
We confirmed the issue was not related to any other plugins, Mod_security, or the the Mail (2) option.
Forum: Plugins
In reply to: [Contact Form 7] Customise SEND buttonHans, I believe these are the two css class selectors you want to edit:
.wpcf7-submit {}
.wpcf7-submit:hover {}Forum: Plugins
In reply to: [Contact Form 7] Contact form 7 stopped working@memmuli I think we may have had the same issue. There was a thread 78 posts deep on the topic that was closed about 20 hours ago.
@buzztone Thank you for posting on these threads about the error message after upgrading to 4.4.1. For us, The new rules released for mod security are not the cause of the issue. We have confirmed with our host running Nginx that they are not using Mod_security.
We’ve deactivated all other plugins including an STMP sending plugin and we are still getting the “Failed to send…” message with WordPress 4.4.1. WordPress 4.4.0 works.
Some users in that previous post mentioned issue related to the the Mail (2) option. We are not using the Mail (2) option.
We had our website name in the From field. We liked having our website name in the From field so that our sales team can more easily see that the email is coming from the website.
Using the default [your-name]<[your-email]> in the From field works but we are hoping that at some point CF7 releases an update that allows us to have our website name in the From field.
Forum: Plugins
In reply to: [Contact Form 7] Form not working after 4.4.1 wordpress updateWe’ve deactivated all plugins except CF7 and we are still getting the “Failed to send…” message with WordPress 4.4.1. Works fine with WordPress 4.4. We are not using the Mail (2) option.
Using the default
[your-name]<[your-email]>
in the From field works but we’d like to have our own custom text in the From field.Looking forward to a CF7 plugin update that allows custom text in the From field.
Forum: Plugins
In reply to: [Contact Form 7] Form not working after 4.4.1 wordpress updateHaving the same issue.
Hi Nishit,
I am using Redis caching and Cloudflare. I’ll try clearing the cache for both and give it another shot.
Thanks!
Works thanks!
Adding
$offer_content = array();
to line no 179 did not resolve the issue.
Deactivating until next version is released.^^ Nice!!!
Thank you for the correction. I wasn’t aware that OAuth 2.0 existed yet for a WordPress SMTP mailer. I’m going to check it out. Bravo Jason!
Hi Jordan,
Are you using Google Apps for Work to have Gmail accounts with custom email addresses (not ending in @gmail.com)?
If so, here’s a couple things that might help:
1) Don’t use an alias address. If your primary email account is [email protected], you may have aliases setup for [email protected], [email protected], and [email protected]. Using one of those alias accounts will not work.
2) Don’t use a group email address. If you have an email like [email protected] that goes to a group of people, you will not be able to enter a unique password for that account because Google’s SMTP server requires authentication. The password for the group owner won’t work either. So, you will need to have a dedicated email address like [email protected] with it’s own password.
Note: If you use this method with a dedicated website email address, make sure to set the “reply-to” to be the user’s name/email and the “from” to be something like ConvertMedia Website <[email protected]>. Otherwise you may end up with emails from something like Mary Smith <[email protected]>.
Also, I’d recommend turning on the vacation notification (in Gmail Settings > General) with a default response letting people know the account is only used for sending emails from the site. This canned response could have contact information listed for company departments.
3) Check to see that you’re allowing non-Google apps to use sign-in technology. To do this in Gmail click on the account icon on the top right corner of the screen (circle shape with a letter or image) > My Account > Account Overview (under Personal info & privacy) > Connected apps & sites (under Sign-in & security) > Allow Less Secure Apps > Turn on. Warning: you will want to use some type of Quiz or reCaptcha when you do this to prevent bots from sending spam from your contact form.
Hope this helps. Cheers!