Closed (fixed)
Project:
Rules
Version:
7.x-2.x-dev
Component:
User Interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Oct 2021 at 05:16 UTC
Updated:
10 Nov 2021 at 22:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tr commentedThis usage of fetchCol() was added to Rules in #1100854: implement tagging support, almost 10 years ago. There is also another place fetchCol() is used improperly and that also needs to be fixed. I find it strange that no one has noticed this before.
What did you do that caused this error? You said "Trying to view rules" but I don't know what that means. Were you trying to create a View? If so, can you export the View so I can try to reproduce this?
Comment #3
selfsimilar commentedSorry for the less than robust bug report. I was pretty tired and wooly-headed when I filed it.
When I say "Trying to view rules", I mean navigating to
/admin/config/workflow/rulesto view the default list of active and inactive rules. Unpatched, navigating to that URL on my system returns the bog standard error 'The website encountered an unexpected error. Please try again later.' and the PDO error is logged. I'm sure my system has some deep issues, as it's over ten years old and migrated from D6, but I haven't tried to recreate this on a fresh install, so I don't have a good way to reproduce the issue. However, fixing the call tofetchCol()addresses the issue for my machine.I'm a bit swamped at the moment, but I'm happy to roll a patch fixing the improper calls to
fetchCol()later this week when my current crisis is more resolved.Comment #4
tr commentedWell here's the patch, it's simple enough and it fixes something that's obviously wrong. I'm just puzzled why it hasn't caused anyone problems in the past.
Comment #6
tr commentedCommitted #4. Thanks for finding this.