You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, we're encountering an issue with the autocomplete functionality where the Ajax calls are being cached, resulting in the same result being displayed every time. Despite changing the parameters, the first result for the autocomplete is cached and consistently returned with each subsequent call. This behavior occurs despite the action being registered as non-cachable and the inclusion of the "noCache" parameter.
This issue also occurs on the example sites provided by this repo.
Steps to Reproduce:
Navigate to the autocomplete search field.
Enter a search query.
Observe that the autocomplete results remain the same even for different queries.
Expected Behavior:
The autocomplete results should reflect the current search query and not be affected by caching.
Additional Information:
We've attempted to resolve this issue by ensuring that the action is properly registered as non-cachable and by including the "noCache" parameter. However, the issue persists.
Proposed Solution:
After further investigation, we found that adding no_cache = 1 in the Setup.typoscript file of the Extension resolves the issue. Here's the modified snippet:
Description:
Currently, we're encountering an issue with the autocomplete functionality where the Ajax calls are being cached, resulting in the same result being displayed every time. Despite changing the parameters, the first result for the autocomplete is cached and consistently returned with each subsequent call. This behavior occurs despite the action being registered as non-cachable and the inclusion of the "noCache" parameter.
This issue also occurs on the example sites provided by this repo.
Steps to Reproduce:
Expected Behavior:
The autocomplete results should reflect the current search query and not be affected by caching.
Additional Information:
We've attempted to resolve this issue by ensuring that the action is properly registered as non-cachable and by including the "noCache" parameter. However, the issue persists.
Proposed Solution:
After further investigation, we found that adding
no_cache = 1
in theSetup.typoscript
file of the Extension resolves the issue. Here's the modified snippet:The text was updated successfully, but these errors were encountered: