[Resolved] View Search Result not Working with Custom Post created with Divi

[Author]

Posts

[ManishT7809]

Tell us what you are trying to do?
I have a view created with Custom Search with Pagination. I have custom post searched with this View. Some of the the custom post I have created with Divi and other with Toolset Layout.
Now When I search using that View it only returns the posts which were created with Toolset Layouts but not the ones created with Divi. What I have debuged with is from the URL.

This URL doesn't work : wpv-wpcf-country=South+Korea&wpv_aux_current_post_id=49891&wpv_view_count=49881

This works : wpv-wpcf-country=South+Korea&wpv_aux_current_post_id=49891

so with wpv_view_count=49881 it doesn't return post created with Divi

Is there any documentation that you are following?

Is there a similar example that we can see?

What is the link to your site?

[Beda]

This is unexpected.
wpv_view_count URL argument is merely used for the View as identifier but not to get or display posts.

Can I ask if you use some AJAX updated Search or Pagination? Those are known to be conflicting in some scenarios with Divi.

Also, please see the new suggested way of using Toolset and Divi here, which is valid if you use Divi 4.0 and above https://toolset.com/documentation/recommended-themes/toolset-divi-integration/
If you still use Divi below 4.0 the older workflow would apply which includes editing Content Templates with the builder directly

If you do not use AJAX and followed above DOC, and the issue still persists, can I eventually see this on a staging site or on a copy (duplicator) as seen in https://toolset.com/faq/provide-supporters-copy-site/?

Thanks!

[ManishT7809]

Hi Beda
Sorry forgot to add the installer. Here's a link

hidden link

Thanks

[Jamal]

Hello! Beda has left the team, so I am taking over some of his tickets. I successfully built a copy of your website and logged into it with a new user. But I don't know which page that contains the view and what are some of the posts that were built with Divi and that do not appear on search results. Can you provide more details and steps to reproduce the issue in such a way as:
1. I go to ...
2. I do ...
3. I expect to have ...
4. Instead, I get ...

[ManishT7809]

Hi Jamal

Sorry I didn't much details in previous message. I think there were some details were missing in the initial file and installer I sent. i have made some changes to the view which needed attention:
View Name:Search Agent ID:60. This update the results if any fiter changes using Ajax.
There are 2 posts in Agents
one for Australia - Created with Divi Editor
one for New Zealand - Toolset Layout

This view is implemented on Home Page - hidden link

Now when I change the country filter from select country -> Australia or New Zealand it changes the URL to
hidden link -- Now If I simply remove the wpv_view_count=60 it works fine and return the result

But If use the View option Full page refresh when visitors click on the search button with input values auto-updating - It returns the results. So something is in the Ajax which causing an issue.

Here're the new links for zip and installer
hidden link
hidden link

Thanks

[Jamal]

Thank you for the details and the new copy. I built it locally and I have now more insights on the problem.

You have used Divi inside the Toolset view "Search Agent" which actually not supported by Toolset.
Check our article about the integration. We have been partially integrating with Divi 3. We are not providing any integration with Divi 4. What we recommend is to use Divi for static pages and Toolset for dynamic pages.
https://toolset.com/documentation/recommended-themes/toolset-divi-integration/

If you want to mix Divi and Toolset on the same page(eg. Homepage), I would suggest using Blocks. Divi has recently released the Divi Layout Block which will let you reuse Divi structures as Gutenberg blocks. hidden link
Check more about Divi and Blocks here hidden link

Please note that, currently, Toolset Views created with blocks do not support filtering on taxonomies yet. This will be released soon. But no estimated date is scheduled.
The workaround is to use the legacy views editor. The one you are using currently for the view.

I hope this helps. Let me know if you have any questions.