Hi @stark
Unfortunately, WPFTS does not work with PODS custom fields "from the box", so custom code exists somewhere. I think your developer used another way to add data to the search index.
We need to ask him or alternatively, I could check your code myself, it should not be too long. In this case please send me admin access to your resource using a private message.
Thanks.
Hi @stark
Yes, as soon as you can show me your custom code for wpfts_index_post hook I think we can detect a problem and fix it.
Thanks!
Hi @stark
Could you test posts 22515 and 11804 on the first tab of the Sandbox? I am curious which data were indexed in those posts, may be the SAME data was indexed for all those posts. The same relevance ratio (80%) is very less probably for such amount of posts.
Also I would see the code you are used to put meta fields to the index. Could you share?
Thanks!
Hi @stark
Thank you for the question!
I think you know how to deal with PODS custom meta fields because I see that you have created clusters with data in the index, and I think it was achieved by the custom code. That's 80% of the job!
As I can see your post records are searchable in the Sandbox by words from the "0" cluster (the custom metafield).
The only problem is you can not get your custom posts shown in the search results on the front page.
This may be caused by a hook in your theme or custom code that intercepts pre_get_posts or another hook related to WP_Query and adds additional filtering to posts either at the input parameter level (for example, it allows searching only posts with post_type = post, page; or adds additional WHERE conditions directly to the query that is formed in WP_Query). I would advise you to review the code of your custom plugins and theme for such hooks. I also recommended that you disable all plugins that may be related to search for testing. For example, Elastic Press.
We are not very familiar with the functionality of PODS, it is obviously similar to the ACF plugin in the database, but it probably also adds some conditions to the search.
The presence of a conflicting hook may also be indicated by the fact that in analytics all queries show either 0 or -1 results, which is incorrect information.
By the way, could you click on any of the rows in the analytics table and see the query details? That might give us a clue as to why this is happening.
Also, give me some time - I need to see if The7 theme conflicts with WPFTS.
Thanks! Let me know if any of the above tips helped you.
Actually WPFTS could be not that great for you in case you have millions of records (e.g. posts).
The whole Wordpress could be not good for you either, because to handle such amount of data you will need to use specific optimization and caching algorithms and even clustering.
I would like to propose you to use full-text solutions based on Apache Solr or Elastic Search - those tools are implemented in Java and work way faster than PHP+MySQL solution provided by WPFTS and they are especially good for big data.
Alternatively you can wait until we release a new WPFTS version (in 1-2 months) that can use self-hosted Elastic Search engine to keep full-text index and uses WPFTS data collecting algorithms.
Thank you for the question.
Hi @jgregory_ca
Okay, the fix for Avada addon should be ready in a couple of days. Just FYI.
Thanks!
Hi @magicalbrad
Many thanks for your report and for sure for your work to fix this issue. We don't face the same on our dev machine that probably caused by version difference or so.
Anyway, I will analyze this problem with deep care and for sure release a new addon version soon.
Thanks!!!
@jgregory_ca
Okay, actually the addon is for different thing. I was just interested if it made this problem or not.
Now I know the reason is not in addon.
Let me make some tests on my dev machine to repeat the bug and find the solution.
Hi, @jgregory_ca
Do you have any WPFTS Addons installed? For example WPFTS Addon for Avada Theme.
Thanks!
