administrators group

EpsilonAdmin

Thank you very much, I am going to examine this theme code and return back with my idea or even Hook code.

Thanks!

EpsilonAdmin

I would be happy to help you with this. As I can see, the theme you created with the given link can be very different. Usually to test and develop a Compatibility Hook I will need to have a theme code closer to that you are using.

So, could you explain how I can create the same (or close) theme that you have to make tests? Or even better if you can send your version of the theme.

Also to test indexing and search without theme clashing I would recommend to use Sandbox Area / Test Search. This tool will return the non-filtered result that is not touched by the theme code.

Please let me know if you can provide more data to me,

Thanks!

EpsilonAdmin

Hi @inkedraskal
Yes, both to highlight results and correct search/indexing.

Let me know if it's not good with your theme.

EpsilonAdmin

Hi @inkedraskal

Thank you for the question. Do you really need to install this hook? It is required only for themes that are incompatible with WPFTS without it.

Do you think your theme is not compatible?

"Unavailable" status means we don't know if this hook is required.

I hope this helps.

EpsilonAdmin

Hi @alihs

I think I know what happens.

There is a "hidden" property of $chunks that we remove when returning array().

This property contains the list of rules applied to the post, and this fact actually forces WPFTS indexer to mark posts as "non-correct" indexed.

This is what I say about:

We have "__used_rules" property in $chunks which we have to store.

Please change your hook code like this

	if ( $date_listing <= $date_now ) {
            // i was returning false here, which i now realize was wrong.
	    return array(
                 '__used_rules' => $chunks['__used_rules'],
            );
	}

I think that should help.

Please try and let me know what happens.

Thank you!

EpsilonAdmin

Hi @alihs

Thank you for your reply!
According to the video you sent it looks like you have around 257 that is constantly refreshing. Those posts are simple and short, and reindeer can refresh them in one internal "tick", but it looks like they are changed very often.

Strange thing, actually!

Could you check the Indexing Rules page where it may show which rule has those 257 unsynced posts?

Also, could you say which 257 posts you have? May be specific post type has exactly 257 records or something.

Thank you!

EpsilonAdmin

Hi @alihs

I hope the code you showed is an excerpt and you still have

$date_now = current_time('timestamp');

somewhere and also your $date_listing value is a Unix timestamp (integer).

For the second case: this AJAX action is used by the WP admin to refresh some index statistics, it does not have any parameters (that's why "z" is empty here).

The message you see means that 257 posts were processed by an outdated version of one or more indexing rules and WPFTS wants to reindex them to bring everything into compliance.
You can open the page with the list of rules and see which indexing rules are not compliant.
You can also send me a screenshot so I can help you figure this out.

By the way, this may be due to the fact that you somehow change some posts from the code, but do not call the "save_post" hook, which triggers reindexing under the hood. Because of this WPFTS considers these posts outdated. If the number of posts controlled by the rule is not 257, then this is exactly the case.

Let me know if you have more information.
Thanks!

EpsilonAdmin

Hi @alihs

Sure, you can do that using the wpfts_index_post hook.

You can implement custom logic inside the hook code and then return normal $chunks value in case you want the Event post to be in the index or return $chunks = array(); (empty array) in case you want to remove the post from the index.

There is no way (by plugin logic) to remove a post from the index completely, but the method above will store an empty record for your expired event, so it will be 100% not searchable and will not take DB space.

Note, another (and more convenient) way to remove posts from the search index is to change their post_status to "draft", for example, and be sure the "draft" status is listed in the excluded list.
It says WPFTS to save only ID information about the post. But without hooks or complex logic.

Let me know if this helps.
Thank you.

EpsilonAdmin

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.

EpsilonAdmin

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!

administrators

Posts

Member List