I’m helping a friend to implement CF7 on a page. I’ve tested the plugin on my own site without any problems.
But with the theme Widely Version: 2.1 it behaves very strange. First of all, I cannot set the css code properly. The theme is someway overriding my custom css attempt.
But more important to solve is that there is no required field protection. You can send a form without writing anything in the required fields. And the message is sent as a query string.
(There is another form plugin installed as well on the site.)

Can anyone help me with this issue?

Torbj?rn

https://www.ads-software.com/plugins/contact-form-7/

The contact form is available on the following page:
https://www.bomasport.com/contact/

After completely filling out and sending the contact form, the arrows start spinning for a while. After this, the arrows dissappear and nothing else happens. The form stays filled in as it is, no message is shown and no e-mail is sent.

I really hope someone can help, thank you!

Best regards,

Metehan

https://www.ads-software.com/plugins/contact-form-7/

https://www.ads-software.com/plugins/contact-form-7/

THIS IS CRITICAL AS SEARCH ENGINES WILL NOT INDEX OR WILL DROP PAGES THAT DON’T DISPLAY SOURCE CODE & TEXT THEY CAN PARSE.

0.9.2.5 Looks like this:

[That’s way too much code to paste here – please use the pastebin – https://pastebin.com/ ; not using code buttons also means your code gets corrupted by the forum’s parser ]

It’s also worth noting that I deleted the whole post, wrote a new one and just wrote “test” in the HTML. It showed up fine on the home page and the actual like. So I went back into the editor and pasted all my HTML for the real post, uploaded it, and then I had the same problem again.

What could be in my HTML that’s doing this? Any help would be greatly appreciated. This is driving me crazy

Old code in wp_die:

if ( !function_exists( 'did_action' ) || !did_action( 'admin_head' ) ) :
	if( !headers_sent() ){
		status_header( $r['response'] );
		nocache_headers();
		header( 'Content-Type: text/html; charset=utf-8' );
	}

New code in wp_die (replace the ":" with "{} open/closing" :
	if ( !function_exists( 'did_action' ) || !did_action( 'admin_head' ) )
        {
	  if( !headers_sent() )
          {
		status_header( $r['response'] );
		nocache_headers();
		header( 'Content-Type: text/html; charset=utf-8' );
	  }
       }

I spend a lot of time cleaning up Authors’ “bad” html, mainly because it affects all previous posts down the page.

One chunk of this issue seems to be that WordPress writes “bad” html, the other is that Authors are not tech savvy and don’t want to open the HTML popup and fiddle with stuff. I don’t blame them.

Is there any PHP tweak or other workaround that might prevent stray “em” or “bold” tags from turning the entire home page into italics, or bold, etc, ie, way beyond the end of the errant post?

Thanks for any insight on this one…

Tbulb