jjchinquist → credited Alexj12 → .
dan2k3k4 → credited Alexj12 → .
dan2k3k4 → credited Alexj12 → .
Just chiming in that I think this would be very helpful to implement. While a number is listed above I believe that the current messaging is not sufficient when a user has the potential of carrying out destructive behaviour on all items in a view.
Will review the solution available as part of an ongoing piece of work in the coming weeks.
Confirming that we ran into this issue recently and during an incident applied the same indexes which resolved the issue. The fact that the current PRIMARY index is composite means it isn't used in the troublesome query.
Reviewed and tested by the community!
John Cook → credited Alexj12 → .
Monitored Room 4 | 3.1 A & B
Monitored Room 3 | 3.5 & 3.6
Monitored Room 6 | 3.1 C & 3.2 C
Monitored Room 5 | 3.2 A & B
Monitored Room 1 | 3.8 The Lounge
Monitored Room 5 | 3.2 A & B
Monitored Room 1 | 3.8 The Lounge
Monitored Room 3 | 3.5 & 3.6!
I attended this!
I suspect @coaston is using https://www.drupal.org/project/eu_cookie_compliance → and I don't believe this is a bug. The 'Drupal.visitor.autologout_login' just needs to be added to its 'Allowed cookies' (and likely to the site's cookie policy).
That cookie is required for the functionality of this module.
If the cookie isn't allowed then it consistently gets removed from the browser and the user is prompted to extend their session repeatedly and logged out if they do not accept.
Thanks for this @dench0, super quick!
Hi @dench0,
This is on 8.x-1.8, with any version of CAPTCHA since 8.x-1.10.
I don't believe the 2.0.x branch is affected, but we can't use an alpha version of a module.
Thanks
This is a relatively quick fix. In my case I haven't had an issue with hook precedence but it _could_ be an issue.
dan2k3k4 → credited Alexj12 → .
Alexj12 → created an issue.
Reviewed and tested as I had actually added an index to the tag table previously but hadn't updated the patch! Thanks!