Plugin conflict

Where can we see the website in question?

You can find my testing website here.

When you choose “Gallery” from the dropdown and then press filter, no results are found, but there are custom posts classified as gallery.
I have the latest version installed of cf7.

When I revert to later versions and without changing anything else, it’s going to work and show me results.

but after investigating further, it seems that the latest update of contact form 7 is causing this problem

Why do you think so?

I’ve been using the same three plugins for a long time with no issues on my main website, but suddenly the filter stopped working. I have the latest versions installed.

But my test website was out of date, so I checked it there.
– old versions (wp,cf7,filter,pods) works fine
– update wp still no issue
– update filter plugin, no issue
– update cf7, filter does not work anymore.
– I checked each version of cf7 and the issue appears using version 5.5.5 and later
– cf7 version 5.5.4 and below are working fine
– updating pods plugin or keeping it old does not change the outcome.
Therefore, I think a change in cf7 version 5.5.5 caused the conflict.

I’m not sure about that.

In the first place, is it really a problem for you? If so, why?

The current version of Contact Form 7 is 5.6.4. Why do you think you need to test with such outdated versions like 5.5.5 now?

Yes, it’s a huge problem. My filter is broken. I have more than thousand posts and visitors can’t use the filter feature anymore because it will always return ‘no result found’.

I know about the current version and I have it installed in my actual live website, which is always up-to-date. But the latest version is breaking the filter.

Why do you think you need to test with such outdated versions like 5.5.5 now?

To explain the issue again:
I have a live website (not the testing one linked in an earlier post), where visitors can filter based on custom taxonomies. It’s an important feature in my website.
I’ve made it using pods plugin and mdtf. I also have cf7 installed and created multiple forms with it.
Everything was working fine. Until some days ago, I realized that it’s not working anymore, and it always returns no result found.

I started investigation the issue:
– deactivated all plugins and reactivated one by one. I’ve found out that cf7 was causing the issue.
– to investigate further without the fear of breaking my website I moved to my test site which I haven’t used for a very long time and all plugins are out of date. With these outdated plugins, the filter was working.
– I updated WordPress core, pods and mdtf and kept cf7 old, the filter was still working.
– So I updated cf7 to see which version first made the problem, and it was 5.5.5. The problem started there. This and any later version breaks the filter. Older versions are working fine.

I don’t want to use the outdated version in my website, but it’s easier to investigate when you know when exactly it happened first.
Some changes made in the version 5.5.5 are conflicting with the filter plugin.

Links:
– Test website where you can filter based on ‘Gallery’. I have about 2-3 posts, but it will show nothing because latest version of cf7 is currently installed.
– Post notifying the mdtf plugin developer about the issue, and I have linked my live website there as well if you want to check it.
On my live website, I even get this error:

WP_Error Object ( [errors] => Array ( [invalid_taxonomy] => Array ( [0] => ??? ??? ?????. ) ) [error_data] => Array ( ) [additional_data:protected] => Array ( ) )

• This reply was modified 2 years, 4 months ago by june01.

I tested a bit more, and I think changes made here are causing the issue.

Hello, I have wordpress with Avada theme, using contact 7 form a lot. Tried to upgrade to 5.6.4 from 5.4. But then all my pages ended up as 404 for some reason. I tried to rollback contact form 7 plugin version down and down to find out which plugin version started this problem and it was 5.5.5. (so at the moment I am at 5.5.4 which works).

Its pure guess, but I also think issue is caused by this “Block editor: Ensures the editor loads the contact forms list by creating inline script on the server side.” somehow.
Another weird effect is that 404 only affect main pages, it does not affect any translated pages https://www.page.com/en/anything .

Apart from 404 there is no error in console/wp admin or anywhere, its like some redirecting issue, I wish I could add some more details but do not know how.

• This reply was modified 2 years, 4 months ago by songoo.

Just a note, I have completely uninstalled contact 7 and installed latest version anew. But it still broken. Maybe 5.5.5+ were never compatible with some wp versions but patcher allowed it go higher hmm ?

UPDATE :
Not really sure how to explain this, but I followed the issue in /block-editor/block-editor.php to

WPCF7_ContactForm::find( array(
			'posts_per_page' => 20,
		) )

When I comment it, page is working when not 404 is shown. Ok so I checked what this returns and on page.com/en it return cf7 array on page.com it returns cf7 array but with additional first item in it, which has everything empty..

So I followed into /includes/contact-form.php to public static function find( $args = ” ) method. I deleted all contact 7 forms in admin, and even then for any magic reason $posts = $q->query( $args ); return Post of “page” type, concretely 404 page post. WTF? , how can WP_Query() return “page” post type when args are [post_type] => wpcf7_contact_form . And I checked, that args looks good :
Array ( [post_status] => any [posts_per_page] => 20 [offset] => 0 [orderby] => ID [order] => ASC [post_type] => wpcf7_contact_form )

This is absolute mystery, and am a bit afraid is more WP related, why would main page query with same args return something else on page.com than on page.com/en .

I solved it, at least for me, but You would have to do it manually in plugin files.

/wp-content/plugins/contact-form-7/includes/contact-form.php

In ‘public static function find( $args = ” ) {‘

Old code is commented out

//$q = new WP_Query();
//$posts = $q->query( $args );
$posts = <strong>get_posts</strong>( $args );

//self::$found_items = $q->found_posts;
self::$found_items = <strong>count($posts);</strong>

Seems somehow, ‘WP_Query()’ is not safe to use and conflicts with some template or other plugins stuff or whatewer, also it can return “404 page” type mixed in query results which just break everything (that was my case).

https://github.com/takayukister/contact-form-7/issues/1001

• This reply was modified 2 years, 3 months ago by songoo.