What other plugins and theme do you use?
HI,
the theme is custom made.
I use the following plugins:
Add From Server
All in one Favicon
All-in-One WP Migration
Contact Form 7
Contact Form 7 Custom Skins
Duplicator
Easy SMTP Mail
Google Analytics for WordPress by MonsterInsights
Lightbox Plus Colorbox
Real 3D Flipbook
TinyMCE Advanced
WordPress Importer
WP-Newsticker
I deactivated already all plugins except Contact Form 7 and Contact Form 7 Custom Skins to check if there are some error with the plugins. But also with the deactivated plugins there is still the same error
Yes, try deactivating all other plugins and switching to the default theme. Of course including the Contact Form 7 Custom Skins.
Tried it already.
When I deactivate contact form 7I do not have the error any more.
The error also do only appear on the subpage where the contact form is embedded.
Hi,
i have the same problem and by mow, no solution found.
kopfkinodesign, could you please advise if you resolve the issue?
thank you
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 8 years, 5 months ago by
kkresge17601. Reason: Missed relevant information about which plugin I was referencing
-
This reply was modified 8 years, 5 months ago by
kkresge17601. Reason: typo