I need to prevent bots and eager users from submitting views filters too often because some of the views are quite complex and require a lot of resources.
Unfortunately, the core views implementation reuses the form-id ('views_exposed_form') for different views, so using different views filters throughout the site are tallied as the same form.
Append form-action (normalized) to form-id for distinction.
Review, approve and merge. I am preparing a patch that will add this option to the Individual Form Configuration section and the related code to append the action string.
I am preparing a patch that will add this option to the Individual Form Configuration section.
Added 'append_action' bool value to the form configuration.
Active
1.0
Code
Adding this patch here in case someone else can use it. The code is sound, but I'm not convinced this solution is complete.
Not sure this is the job of this module. Should be more relevant to improve form ids for view exposed form no ? And to have, as for node form for example, a base form id (the current one) and a specific form id for the given view. But this is a core issue.