Closed NowhereWM closed 1 year ago
For what it's worth, you missed providing the link to the site in question.
To be certain, you've provided the complete index name for the replica indexes for the sortBy widget, correct? For example, do they have the alg_
prefix as well?
Hello, the website link is auto-motive.gr.
I have used the name of the index, for example it's price_replica and price_replica_desc as they appear inside algolia.
Xenofon
On Mon, Oct 16, 2023, 16:39 Michael Beckwith @.***> wrote:
For what it's worth, you missed providing the link to the site in question.
To be certain, you've provided the complete index name for the replica indexes for the sortBy widget, correct? For example, do they have the alg_ prefix as well?
— Reply to this email directly, view it on GitHub https://github.com/WebDevStudios/wp-search-with-algolia/issues/382#issuecomment-1764507532, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDJF3MNJUJJSWZ7UD7B3X4LX7U2KHAVCNFSM6AAAAAA6BFOVKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUGUYDONJTGI . You are receiving this because you authored the thread.Message ID: @.***>
I don't believe you need to be creating the <select>
markup yourself, just providing an empty div like <div id="sort-by"></div>
would be enough for Algolia's widget to find and render the dropdown for you. Give that a try and let me know if it resolves things.
I am using these now:
instantsearch.widgets.sortBy({
container: '#sort-by',
items: [
{ label: 'Default', value: 'alg_searchable_posts' }, // Main index
{ label: 'Price (Low to High)', value: 'price_replica' }, //
Replica for ascending price { label: 'Price (High to Low)', value: 'price_replica_desc'}, // Replica for descending price // Add more sorting options as needed ] }),
And it's not sorting again :/ I removed the html selector, I attach you our current php of instantsearch
Επισκόπου Αμβροσίου 6 Θεσσαλονίκη, Ελλάδα
@. @.> + 30 23 11 11 88 30 <+302311118830> www.nowhere.gr http://www.nowhere.gr*
On Mon, Oct 16, 2023 at 5:59 PM Michael Beckwith @.***> wrote:
I don't believe you need to be creating the
— Reply to this email directly, view it on GitHub https://github.com/WebDevStudios/wp-search-with-algolia/issues/382#issuecomment-1764675895, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDJF3MO2FUP75BD4KMCA4QDX7VDWVAVCNFSM6AAAAAA6BFOVKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUGY3TKOBZGU . You are receiving this because you authored the thread.Message ID: @.***>
Also I am not sure if we also need to have the "woocommerce-algolia" plugin, we found it in one of your posts. We are currently using "WP Search with Algolia" and "WP Search with Algolia Pro". We also have an issue not indexing all our products from yesterday maybe this is also linked to the sorting problem.
Επισκόπου Αμβροσίου 6 Θεσσαλονίκη, Ελλάδα
@. @.> + 30 23 11 11 88 30 <+302311118830> www.nowhere.gr http://www.nowhere.gr*
On Mon, Oct 16, 2023 at 6:11 PM Nowhere Web Management @.***> wrote:
I am using these now:
instantsearch.widgets.sortBy({
container: '#sort-by', items: [ { label: 'Default', value: 'alg_searchable_posts' }, // Main index { label: 'Price (Low to High)', value: 'price_replica' }, //
Replica for ascending price { label: 'Price (High to Low)', value: 'price_replica_desc'}, // Replica for descending price // Add more sorting options as needed ] }),
And it's not sorting again :/ I removed the html selector, I attach you our current php of instantsearch
Xenofon
Επισκόπου Αμβροσίου 6 Θεσσαλονίκη, Ελλάδα
@. @.> + 30 23 11 11 88 30 <+302311118830> www.nowhere.gr http://www.nowhere.gr*
On Mon, Oct 16, 2023 at 5:59 PM Michael Beckwith @.***> wrote:
I don't believe you need to be creating the
— Reply to this email directly, view it on GitHub https://github.com/WebDevStudios/wp-search-with-algolia/issues/382#issuecomment-1764675895, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDJF3MO2FUP75BD4KMCA4QDX7VDWVAVCNFSM6AAAAAA6BFOVKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUGY3TKOBZGU . You are receiving this because you authored the thread.Message ID: @.***>
I know I have some blog posts on our WebDevStudios blog about Woocommerce details, and a lot of that got rolled into our Pro plugin. Otherwise, I'm not quite sure what woocommerce-algolia you're referring to.
The only Algolia plugins that we actively support ourselves will be both WP Search with Algolia, and WP Search with Algolia Pro.
I'm still seeing the self-typed up select input when I look at the site and view-source. Is it possible you need to do a cache clearing?
I just cleared cache.
Xenofon
On Mon, Oct 16, 2023, 18:25 Michael Beckwith @.***> wrote:
I know I have some blog posts on our WebDevStudios blog about Woocommerce details, and a lot of that got rolled into our Pro plugin. Otherwise, I'm not quite sure what woocommerce-algolia you're referring to.
The only Algolia plugins that we actively support ourselves will be both WP Search with Algolia, and WP Search with Algolia Pro.
I'm still seeing the self-typed up select input when I look at the site and view-source. Is it possible you need to do a cache clearing?
— Reply to this email directly, view it on GitHub https://github.com/WebDevStudios/wp-search-with-algolia/issues/382#issuecomment-1764736758, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDJF3MIYV5YECRGVBZQHZIDX7VGXDAVCNFSM6AAAAAA6BFOVKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUG4ZTMNZVHA . You are receiving this because you authored the thread.Message ID: @.***>
still seeing this in the view-source:
<div class="sort-by-wrapper">
<label for="sort-by">Sort by:</label>
<select id="sort-by">
<option value="alg_searchable_posts">Default</option>
<option value="price_replica">Price (Low to High)</option>
<option value="price_replica_desc">Price (High to Low)</option>
<!-- Add more sorting options as needed -->
</select></div>
as opposed to
<div id="sort-by"></div>
like the documentation generally leans towards.
Fixed! We had another file loaded on the child theme :)
We also fixed the importing issue.
Some more questions: 1) Images we used this code you suggested to change the sizes we sent to algolia. What we need is to push the correct size (full) to our main products because now it's mixed, some products on instant search results return thumbnails and others return the correct size (650x650). Is there a way to control the image size we push to algolia? 2) We find it difficult to add a correct "add to cart button" to add the product from search results to our cart. Do you have any documentation that might help us? 3) Where should we look for documentation, directly in Algolia or on your Github? 4) How can we add elements to the product loop? We want to display the brand Icon inside instasearch product results. Which template are you using in your plugin for the product loop? 5) Finally, do you have a guide or plugin that could help us configure the " events" algolia suggests us to use? We want also to use the "recommend" feature algolia offers besides "search".
Thank you very much for your help, I appreciate it.
Επισκόπου Αμβροσίου 6 Θεσσαλονίκη, Ελλάδα
@. @.> + 30 23 11 11 88 30 <+302311118830> www.nowhere.gr http://www.nowhere.gr*
On Mon, Oct 16, 2023 at 7:03 PM Michael Beckwith @.***> wrote:
still seeing this in the view-source:
as opposed to
like the documentation generally leans towards.
— Reply to this email directly, view it on GitHub https://github.com/WebDevStudios/wp-search-with-algolia/issues/382#issuecomment-1764805550, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDJF3MLBLOIAY72VK2CNMK3X7VLCHAVCNFSM6AAAAAA6BFOVKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUHAYDKNJVGA . You are receiving this because you authored the thread.Message ID: @.***>
First I can see for any issues around importing, but good to hear that's presently resolved.
[ 'thumbnail', 'full' ]
and it'd index both. as part of the images
property in the Algolia Index. The other is a bit more of a generic one where you can specify a URL, width, and height, for an image. I just opened an enhancement issue for this 2nd filter to get the post ID passed as an extra parameter. Using the first filter will be more advantageous right now.href="https://yourdomain.com/?add-to-cart=25&quantity=1"
with the 25 from this example string being replaced with {{ data.post_id }}
as part of the hit template area. Example: href="https://yourdomain.com/?add-to-cart={{ data.post_id }}&quantity=1"
instantsearch.php
and autocomplete.php
are general PHP files that we load, and let Instantsearch and Autocomplete javascript libraries do their thing. See: https://www.algolia.com/doc/guides/building-search-ui/what-is-instantsearch/js/ and https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/autocomplete/js/Most of our documentation is going to be more around indexing and index/settings management via code.
data
object that is returned and rendered with each hit. You can add new properties via the "shared attributes" filter setup, some quick examples can be found at https://github.com/WebDevStudios/wp-search-with-algolia/wiki/Custom-Attributes but let me know if you need something a bit more specific.Closing as there's nothing actionable from us with the plugin. Discussion can continue.
Describe the bug I am trying to create a sortBy widget for instant search results with the options: a) price ascending b) price descending and c) Default value. It is a woocommerce store (wordpress) or you can try directly this link . . I have followed All the instructions from this page . I am also using wp-search-with-algolia-pro plugin.
To Reproduce Steps to reproduce the behavior:
Additional context My current code on instantsearch.php template is: