Jon Dingman

This worked perfectly. Thanks @richaber!

@tw2113 any further thoughts? TIA!

@tw2113 Thanks – I tried that with no success.

I found an implementation that someone else wrote too, which looked close

https://gist.github.com/rayrutjes/6b1de96b3687b937086428c37bf144f9

Just not sure how to implement this into a single index or have it query the two indices.

Simply don’t want to use the “all posts” because it defeats the purpose of selecting my own.

I’m using a frontend implementation of instantsearch to connect to my index as well.

@tw2113 Ah good find. Are you thinking that I Would apply the filter of algolia_searchable_post_types and simply pass in the post types I want to search on?

Ah I think I know what’s going on actually. I have just the prefix in the code, and I need to add “_searchable_posts” to it.

@tw2113 I’m running into separate issues now with the prefix you mentioned above, I noted it on github.

https://github.com/WebDevStudios/wp-search-with-algolia/issues/93

@tw2113 additionally, I have my own search.js file which I’m loading up with some customizations, since I’m not using the native search functionality. I built my own and connected it to Algolia.

The problem I’m trying to solve is that, at the moment, the app IDs and keys are hard coded into search.js (file I created), is there a better way to manage this across environments?

const searchClient = algoliasearch( “8D1B221KTYC”, “235cde75a1b422212811408d39ac8d” );

const search = instantsearch( {
indexName: “localnew_searchable_posts”,
searchClient,
searchFunction( helper ) {
// Ensure we only trigger a search when there’s a query
if ( helper.state.query ) {
helper.search();
}
},
} );

Also to localize the indexName so it’s for that particular environment.

Thoughts?

I did a search in my webserver folder via egrep, but nothing found for that error. Also reviewed the error logs, nothing for that.

I can access my site over SSL through a locally trusted SSL cert via LocalWP, but I certainly could see how that might be an issue based on what you’re describing.

What’s next?

It happens each time that I upgrade the plugin.

I’m using LocalWP for my environment

Here is my Site Health output

https://gist.github.com/dingman/3383e0b0a569fec6dd1ac3b41dba9ce2 (will delete after issue is resolved)

Any updates to this? I can’t upgrade my plugin to the latest because it breaks the connection, really hoping to get a resolution

Thanks!

That should work, thank you!

@richaber I’ve yet to upgrade again since it stops working in 1.4, any suggestions how else I can debug the issue?

What you stated is accurate. It’s looping through a single thumbnail to get the image. If you want to push additional images to the index in Algolia, you need to add them.

Solution URL: https://discourse.algolia.com/t/image-size-on-instantsearch-page/1593

Actual solution:

add_filter('algolia_post_images_sizes', function($sizes) {
    $sizes[] = 'medium'; 

    return $sizes;
});

• This reply was modified 4 years, 3 months ago by Jon Dingman.

Thanks Michael. Are you stating that the codebase should already be indexing all associates images, or I would need to write custom code to handle that?

I’m using LocalWP for my development environment, no proxy that I’m aware of.