See below for the fix:

Fortunately, it is easy to turn it off, add the following line to your wp-config.php file:

define( 'WPCF7_AUTOP', false );

You can also use a filter in your theme (functions.php) or your plugin:

add_filter('wpcf7_autop_or_not', '__return_false');

The last snippet does the some but it attach the code to the theme and not to the WP instance.

Contact form code:

<div class = "cf7-single-row-flex">
	<label class = "cf7-fi">[text* your-name placeholder "Name"]</label>
	<label class = "cf7-fi">[email* your-email placeholder "Email address"]</label>
	<label class = "cf7-fi">[tel your-phone placeholder "Phone no."]</label>
	<div class = "cf7-fi-submit">[submit "Contact Me"]</div>
</div>

CSS code:

.cf7-single-row-flex
{
	display: flex;
	column-gap: 10px;
}

.cf7-fi
{
	min-width: 0 !important;
	flex: 1.5;
}

.cf7-fi-submit
{
	flex: 1;
}

.cf7-fi-submit input
{
	width: 100%;
}

.wpcf7-spinner
{
	display: none;
}

How it originally looked like: https://i.imgur.com/okPfhNs.png

How it looks like on CF7 5.7: https://i.imgur.com/eikWMiZ.png

For now, I have manually installed 5.6.4 and disabled auto updates.

I have errors on my website with the W3C validator because of your plugin.

Error displayed is “No p element in scope but a p end tag seen.”

It come from admin/modules/settings-popup/views/cookie_settings.php at line 95:
The do_shortcode( $category_description, 'cookielawinfo-category' ) can contain a table (block element) that cannot be inside a <p> tag (invalid markup).

See: https://stackoverflow.com/questions/21084870/no-p-element-in-scope-but-a-p-end-tag-seen-w3c-validation

A solution can be to replace <p> tag by a <div> tag.

Can you fix this and add it to next release?

Thank you

I have created a custom template for textlinks to amazon products, which I want to show within my texts. In pages this is working fine, as expected.

However, in blog posts the same short code gets a closing </p> tag before it and an opening <p> tag after it, so that my textlink, which is supposed to be in the same line as its surrounding text is now in a separate line.

How can I make this work in blogposts, too, to keep the shortcode output in line with the surrounding text?

Compare the blogpost
https://hundebetten.shop/warum-kratzt-mein-hund-in-seinem-bett/#buchtipp (not working)
with the page
https://hundebetten.shop/bestseller/#comfort (working)

Again, these links are created with the identical shortcode.

I already tried to add the lines

remove_filter('the_content', 'wpautop');
add_filter('the_content', 'wpautop', 12); 

to my functions.php, but the only effect was that it made the problem appear in the page, too.

Thanks in advance
Sascha

When I validate my site with https://validator.w3.org/nu/?doc=https%3A%2F%2Fweddingreport.nl%2Ftest%2F I run into a couple of errors. One of them seems related to pop-up builder.
It says “Error: No p element in scope but a p end tag seen.”
I’ve tried narrowing the causes down by creating this test page https://weddingreport.nl/test/
This one has a pop-up with just text when you click the left button. This one generates no error. The button on the right gives the source code the generates the error. One could think it is caused by wpforms, because it contains the form. However, I did also make a page with just the form https://weddingreport.nl/test-2/ and tested it in the validator. That page has no error.

Can you please help me?

The line: p{margin: 0px !important;} causes formatting problems on various pages throughout my site. Removal of this line fixes problems (as does deactivation of JS Support).

Seems global changes, especially with “!important”, should be avoided in any plugin.

Great plugin in general!

I am adding Gutenberg support to one of my themes.

It’s adding p and br tags on custom post type loop.

How can I avoid those tags?

Screenshot: https://puu.sh/AYvSq/07781532ee.png

Thanks

It seems that when I enter text into the WYSIWYG editor, in both text and full mode, the first paragraph goes outside of the p tag and and all other paragraphs are in between <p></p> tags correctly.

Can anyone shed some insight on this?

Here is the screen shot: https://wpsprockets.com/images/p-tag-error.png