Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a view displays an exposed filter or some other sort of form (e.g. Webform node) it becomes problematic if you use the time-based views caching for its output. You get forms pre-filled with other users' search terms/data and "illegal choice has been detected" whenever they are submitted.
It'd be cool if Views could somehow be smart about this and disable the renderable output caching option in the event that <form>
appears in its output somewhere.
Comments
Comment #1
iamjon CreditAttribution: iamjon commentedAssigning to merlinofchaos for review
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedHmm. The actual exposed input used should be part of the cache key, so I'm surprised that this happens. You shouldn't get other users input in the exposed form.
Comment #3
dawehnerMh
That's all get parameters which are used here.
Comment #4
tomgf CreditAttribution: tomgf commentedCheck out this topic: #1055616: Query arguments should be replaced before generating cache ID.
Comment #5
johnvmarking as duplicate of #1055616: Query arguments should be replaced before generating cache ID