Encountered this issue after upgrading a site from 10.2.x to 10.3.x which included bumping this theme to 3.32.
Even down to trying out the previous advice 'In my case, removing this file bootstrap/templates/block/block.html.twig
resolved the update.php issue.' which worked, but I wasn't too keen on that as a permanent fix.
I'm entirely sure that all composer commands were run successfully when the issue occurred, but I simply re-ran `composer require 'drupal/bootstrap:^3.32', composer re-evaluated and regenerated a number of autoload files and following that database updates ran successfully. The issue seems to be resolved for the site that was affected.
This might sound like I missed something, and maybe I did, but I haven't been able to track down what. May just be worth a try as a first pass if anyone else runs into this issue.
breidert → credited alexj12 → .
dan2k3k4 → credited alexj12 → .
Monitored 'Migrating the A11yTalks Website from React Components to Single Directory Components' and 'Ahead of the Curve: The Power of Shift Left in Ensuring Quality'
Monitored 'Practical exploitation of Drupal security vulnerabilities'
Monitored 'Everything you need to know about cookies but are afraid to ask!' & 'Accessibility Beyond Compliance: Practical Insights for Drupal Users and Editors'
I monitored 'The final hurdle: Empowering and supporting your pitch team towards success' and 'Drupal Staff Augmentation: Doing it right for Customer Delight'!
I monitored 'Developer Debugging Toolkit: Practical Techniques for Debugging Drupal Cache Problems'!
I attended this!
Volunteered for this slot.
Monitored 'Designing for Privacy: Techniques and Methodologies for Balancing User Needs and Data Security'!
Monitored 'Lessons from 12 years of mapping animals in and out of Drupal'!
Monitored 'AI with Drupal - Using LLM technology is easy, but how do you actually build useful applications?'!
Monitored 'Let's try to understand Typed Data, finally...'!
Just linking commit 539edcf2cfe124f4e046f553b16c85982498cd4f as I believe this shows that the lack of application of these settings to on-prem is an oversight rather than being purposeful, as the connection condition contains a return which has not been touched.
amateescu → credited Alexj12 → .
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!