kkresge17601

Hey guys, I wanted to say thanks – it made me double check some things with our custom theme. You plugin works great, BTW and I appreciate it. Our forms look better as a result.

I edited the php blade used to build those particular pages and it turns out that something about switching from the blade calling the shortcode as field data, rather than putting in legacy php to generate the shortcode fixed the issue. So it was definitely something on our end.

Thanks again!

This is a ridiculous change. I’ve read Google’s articles on this.

Your own article on the update to 17.1 says, and I quote, “…because Google seems to change these…” (emphasis mine).

Nowhere in ANY Google documentation that I can find do they state that they are removing or replacing these symbols. In fact, their articles repeatedly state that they may replace the entire title if their algorithm thinks that your title is not correct or “good enough”, basically.

Your decision to remove this without warning is causing me to have to manually add code to literally HUNDREDS of websites that I manage. I would urge you to reconsider this change as it is not founded in ANY factual statement from Google regarding their new title protocols.

The issue isn’t from CF7 directly that I found. It’s coming from the CF7 Custom Skins plugin that my client had installed. I modified the contact-form-7-custom-skins.php file and removed this error as the developer hasn’t gotten around to it.

Around line 281 this is what now appears in my modified version:

$wpcf7_form='<div class="cf7ct_form'.$atts['id'].'"><div id="form_header">'.$data["hd_cnt"].'</div><div class="cf7ct_form_wpcf7">'.do_shortcode("[contact-form-7 id=\"".$shortcode_id."\"]").'</div><div id="form_footer">'.$data["ft_cnt"].'</div></div>';
		/* Original variable - modified to remove error from form $wpcf7_form='<div class="cf7ct_form'.$atts['id'].'"><div id="form_header">'.$data["hd_cnt"].'</div><div class="cf7ct_form_wpcf7">'.do_shortcode("[contact-form-7 id=\"".$shortcode_id."\"]").'<input type="hidden" value="'.$security_token.'_'.$atts['id'].'" name="cf7ct_security_token" id="cf7ct_security_token"></div><div id="form_footer">'.$data["ft_cnt"].'</div></div>'; */

I retained the original line as a reference, but removed the call for the security token to be dropped into the form output. This removed the giant “BAD REQUEST” h1 and the error code.

• This reply was modified 7 years, 2 months ago by kkresge17601. Reason: Missed relevant information about which plugin I was referencing
• This reply was modified 7 years, 2 months ago by kkresge17601. Reason: typo

I modified the contact-form-7-custom-skins.php file and removed this error as the developer hasn’t gotten around to it.

Around line 281 this is what now appears in my modified version:

$wpcf7_form='<div class="cf7ct_form'.$atts['id'].'"><div id="form_header">'.$data["hd_cnt"].'</div><div class="cf7ct_form_wpcf7">'.do_shortcode("[contact-form-7 id=\"".$shortcode_id."\"]").'</div><div id="form_footer">'.$data["ft_cnt"].'</div></div>';
		/* Original variable - modified to remove error from form $wpcf7_form='<div class="cf7ct_form'.$atts['id'].'"><div id="form_header">'.$data["hd_cnt"].'</div><div class="cf7ct_form_wpcf7">'.do_shortcode("[contact-form-7 id=\"".$shortcode_id."\"]").'<input type="hidden" value="'.$security_token.'_'.$atts['id'].'" name="cf7ct_security_token" id="cf7ct_security_token"></div><div id="form_footer">'.$data["ft_cnt"].'</div></div>'; */

I retained the original line as a reference, but removed the call for the security token to be dropped into the form output. This removed the giant “BAD REQUEST” h1 and the error code.