Looper Consumer does not respond to new/modified query

Support
#1

I am attempting to modify the query results within a Looper via a couple of dropdown selections.

Once both selections have been made, I want to refresh the query to display the results. In this case, a single result.

The selections are WC Product Global Attributes.

Currently, I can disable the Looper Provider and use the selections in a URL parameter string to load the query on initial page load, but I cannot get the query to update on an AJAX call. The selections also modify the URL string correctly, but the Looper keeps the results of the initial query.

Any thoughts or insight into getting the Looper to accept the new query?

Here is the example: The original query is for 9 Holes and Junior selections. The selections were changed to 18 Holes and Adult, but the result did not change after the query updated.
image

#2

Hello @mediaryte,

Thanks for writing in! With what you are trying to do, you will need a custom javascript AJAX coding that monitors any events over the dropdowns. As soon as you have selected the dropdown, the JS script will trigger AJAX call. Regretfully, this particular customization request is outside the scope of our support as this is not related to an issue with the theme and instead has to do with your customization of it. As such, you will need to investigate this particular issue on your own or seek help from a developer should you not feel comfortable making these changes yourself. If you have any further questions about the theme, we are more than happy to provide you with assistance on these inquiries.

Thank you for your understanding.

#3

Hi @ruenel - thank you for the response. I should clarify that the current AJAX call does update the query on the WC shop and product archive pages correctly when a Looper is not used. However, when using the a Looper, the AJAX call is ignored.

It appears the Looper is not listening for AJAX events. Is it possible to introduce this functionality?

#4

Hi @mediaryte,

The loopers are just intended for displaying the content. As my colleague said, the one you are requesting is beyond the scope of your theme support because it will require some custom code to get the correct functionality.

On the other hand, I create a feature request so it might be taken into account in the future.

Thank you.

1 Like
#6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.