[pbaines]

Brilliant, thanks! Just adjusted the search instance keyword exceptions list and lts now showing results, even for longer titles.

[pbaines]

Great, that fixed it! I’ll deploy it to live, thanks.

[pbaines]

Hi Ernest,

Unfortunately, the errors are still persisting.

I updated the plugin on staging.ispnlibrary.org and cleared the browser cache, deleted all files from /wp-content/cache/asp. We don’t have any other caching running on the staging server. I also tried a private browser window but still no luck.

frontend username: ispn-admin
frontend password: mrq4QDW*jua0qdn@zpc

Note: live is still 4.26.11 as I wanted to run tests on staging before deploying.

Let me know if you need access to the Staging server and I’ll create a login.

Best,

Peter

[pbaines]

You cannot access this content.

[pbaines]

You cannot access this content.

[pbaines]

You cannot access this content.

[pbaines]

You cannot access this content.

[pbaines]

You cannot access this content.

[pbaines]

You cannot access this content.

[pbaines]

Thanks Earnest,

Just out of interest, would we be able to apply a temp fix for this using the javascript API and getting the result count?

My thoughts are…

Search, if load more button does not appear, results count message will read Showing X results

Search, if load more button does appear, results count message will read Showing first X results

I’ve been trying to tap in to the search using the javascript API but can’t seem to get a result count from anywhere. Perhaps you could point me in the right direction?

[pbaines]

Thanks Earnest, I get that this search is already quite resource-heavy, so in some ways this does make sense. Please keep us posted if you do find another less resource-heavy method of getting this count, but in the meantime, we’ll look into other options.

[pbaines]

Amazing, I think thats fixed it! Thanks a lot.

I’ve performed some of the same searches and the issue has stopped occurring.

Can you let me know what you added so that I can move to my local?

Best,

Peter

[pbaines]

Hi Earnest,

Thanks for taking a look, and strange that you can’t recreate.

I’ve tried the following:

– Updated the plugin (4.26.11)
– Disabled index table engine and reenabled
– Disabled caching
– Cleared WPEngine cache

I’ve attached a video of what we’re seeing, reported across multiple devices in multiple locations.

There must be something strange going on with the index table engine, as I cannot recreate this with the regular engine. We can swap back to the regular engine, but that means we cannot use some of the features of the index table engine, such as synonyms.

If there is another way to speed up the search instead, and retain the features within the index table engine, we can use that.

[pbaines]

You cannot access this content.

[pbaines]

Thanks Earnest, we re-enabled and made some settings tweaks, and the search seems to be as accurate and definitely faster.

The only slightly strange issue that we’re seeing is the custom results template that we were using, within the child theme in asp/vertical.php no longer seems to be getting used, and results are defaulting to a stacked layout.

To add some context, this only seems to be happening when just ‘page’ post types are found. If the results contain ‘pages’ and another post type, our custom template is shown.

Does the template change with the index table results for pages?

• This reply was modified 2 years ago by .

[Author]

Posts