Forum Replies Created
-
Posts
-
Okay, my apologies. I have one more update:
I toggled OFF the “Search in content” toggle and that fixed it. Now the correct post appears in the correct spot. But I’m still confused as to why “1200” brought up ALL the included pages when content toggle was on, especially when I couldn’t find that string on some of those pages. If you have any input on that, let me know. For now, I’ll just keep that “search in content” toggle off, although I liked the idea of having that on at some point so descriptive text on product pages can be taken into account.
Okay I need to update this. I realized something:
It appears that the correct product is displayed, but it is displayed at the very bottom in a second “Results from Products” section. So I guess my new question is: why is this result not the highest in the order? And why exactly are all these other results being triggered? You’ll notice if you type various other numbers, very few “pages” appear in the results, but for this numeric string (1200) every included page appears in the list. Seems something is not right. Usually if the search string corresponds to a “models” tag on a product page, then that product appears highest priority. Screenshot attached.
Hey Ernest, please take a look at this one and hopefully it will clarify: https://somup.com/cT1FlTLOdj
It does give you a view in the GTM preview/debug window as to which asp_events are triggering and whether or not that is what should be happening. As I mention in the video, I know it isn’t in the scope of your support to setup my GA4/GTM but I’m wondering if the search_start event is being triggered incorrectly even though I have it disabled in my settings.
I’ll also add that I’m getting those “Phrase: {phrase}” entries for every additional key that is pressed for a query. So if someone types “pt2448” I will get a whole list of events in GA4 for “pt” and “pt2” and then “pt24” “pt244” and so on. Definitely would like to turn that off if possible.
Thank you Ernest, that all makes sense regarding the live load. Divi Machine does seem to operate on query loops, I’ll be okay without that. As for the second explanation, I actually think I read about that (inability to match terms within words with index table engine) and must have forgotten, I am trying to learn the various aspects of the plugin as I go but it is pretty deep so I appreciate your patience. We will proceed without the functionality we have, as we are still leaps and bounds ahead of the old tools.
Excellent. This all makes sense. One issue I bumped into was that after I got it working (using your DOM selector provided above) it did load the results into the main grid as expected, but it loaded all of our “blog” posts and not any of the posts that the search instance is configured to index. Same search bar works okay when deployed without the archive “live load” functionality, loading the CPT “resources” which is the only one it is configured to display. But when the live load is enabled, it loads standard “blog” posts instead.
I may not go with this use case in the end, so please don’t put too much time to it, but if you have an easy answer for that please let me know so I can continue experimenting.
I did delve into this page: https://documentation.ajaxsearchpro.com/behavior/results_page_live_loader
I tried configuring the archive live loader and specifying the DOM element as .et_pb_blog_grid and it looked like it was trying real hard to load filtered results into that element but it looks like the filtering options would remain the same even if it had worked.
Perhaps I need to simply use Ajax Search Pro on the main, broad level resources page and if someone starts drilling down just use a traditional list of categories on the left.
Thank you Ernest. You offer some of the best support out of all the plugins (and many other non-WordPress technologies) that we use.
Thank you for all these possibilities. Great suggestions! At least helps me see I wasn’t missing something obvious. I will experiment with them and see which is the best for our setup. We can close this one now.
Ernest,
Thank you so much for looking into this so thoroughly. I will send this on to Divi and see if I can get a response as far as Divi 5 goes. I appreciate you trying all the options presenting me with possible workarounds. I may toy with some of it depending on what Divi says. I’ve been meaning to create a child theme anyhow.
