-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caching issue when list view is initially called without filter #12
Comments
Unfortunately i currently have no idea how to properly fix this, but if Georg or someone else has any suggestions i could try to fix it and create an PR. |
Same here. It is not the best solution but I fixed it with the following typoscript: // Disable caching if search params set |
My solution also doesn’t work now, I don’t know why and why it has worked some time ago. When setting [traverse(request.getParsedBody(), 'tx_news_pi1/search/subject') || traverse(request.getParsedBody(), 'tx_news_pi1/search/fromDate') || traverse(request.getParsedBody(), 'tx_news_pi1/search/toDate') || traverse(request.getParsedBody(), 'tx_news_pi1/search/filteredCategories')] then it works (only with config.no_cache = 1 and COA_INT didn’t solve it). A proper solution for this would be great. |
In ext_localconf.php the list action is added to the list of non-cachable actions only when a search POST var is set:
Because ext_localconf.php is only called once and then cached this leads to caching issues, when the list page with filters is initially called without any filter, because the list action is not added to the list of uncachable actions and filters do not work.
The text was updated successfully, but these errors were encountered: