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.Upon upgrading 1.3 to 1.5 I received this error. It's a fatal error and causes the page to not function at ALL and is therefore a critical issue.
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'title' in 'field list': SELECT DISTINCT(SUBSTR(title, 1, 1)) AS prefix FROM {taxonomy_term_data} WHERE tid IN ( :nids_0, :nids_1, :nids_2, :nids_3, :nids_4, :nids_5, :nids_6, :nids_7, :nids_8, :nids_9, :nids_10, :nids_11, :nids_12, :nids_13, :nids_14, :nids_15, :nids_16, :nids_17, :nids_18, :nids_19, :nids_20, :nids_21, :nids_22, :nids_23, :nids_24, :nids_25, :nids_26, :nids_27, :nids_28, :nids_29, :nids_30, :nids_31, :nids_32, :nids_33, :nids_34, :nids_35 ); Array ( [:nids_0] => 601 [:nids_1] => 600 [:nids_2] => 602 [:nids_3] => 603 [:nids_4] => 604 [:nids_5] => 605 [:nids_6] => 606 [:nids_7] => 607 [:nids_8] => 608 [:nids_9] => 609 [:nids_10] => 610 [:nids_11] => 611 [:nids_12] => 612 [:nids_13] => 613 [:nids_14] => 614 [:nids_15] => 615 [:nids_16] => 616 [:nids_17] => 617 [:nids_18] => 618 [:nids_19] => 619 [:nids_20] => 620 [:nids_21] => 621 [:nids_22] => 622 [:nids_23] => 623 [:nids_24] => 624 [:nids_25] => 625 [:nids_26] => 626 [:nids_27] => 627 [:nids_28] => 628 [:nids_29] => 629 [:nids_30] => 630 [:nids_31] => 631 [:nids_32] => 632 [:nids_33] => 633 [:nids_34] => 634 [:nids_35] => 635 ) in alpha_pagination_handler_pagination->getEntityPrefixes() (line 572 of sites/all/modules/contrib/alpha_pagination/views/alpha_pagination_handler_pagination.inc).
Reverting it back to 1.3 the error disappears.
| Comment | File | Size | Author |
|---|
Comments
Comment #2
ElusiveMind CreditAttribution: ElusiveMind commentedInteresting. Must have something to do with the Taxonomy entity type. I'll look at this deeper tonight when I get out of work. Thank you for the heads up.
Comment #3
ElusiveMind CreditAttribution: ElusiveMind commentedThis is interesting because the module wasn't designed for Taxonomies... now... that doesn't mean it can't work - I'm just not sure how it ever did since Taxonomy term entities key off "name" instead of "title".
I've made a fix, but I am not sure it applies to your situation. Did you define a taxonomy view and set up your contextual filter to key off taxonomy term name?
I'm digging deeper but this may be more than I can accomplish tonight. Hopefully I can roll a patch tomorrow or Thursday that can bet tested.
Comment #4
crystaldawn CreditAttribution: crystaldawn commentedHere is the view that causes the issue when attempting to upgrade. It works ok with 1.3, but upgrade to 1.5 and things head south like a flock of geese :D
Comment #6
ElusiveMind CreditAttribution: ElusiveMind commentedI just rolled a new dev version of the module with a potential fix (your view code helped! thanks!).
Would appreciate if you could test in a dev environment and report back.
Comment #7
crystaldawn CreditAttribution: crystaldawn commentedThe dev version now works with the view. So whatever you did has fixed the issue.
Comment #8
markhalliwellComment #12
crystaldawn CreditAttribution: crystaldawn commentedI ran across this yet again and it appears that you missed 1 extra place where the title needs to be switched to 'name'. Attached is an example patch that does just that. I am unable to re-open this task as it's set to maintainers only.
Comment #13
ElusiveMind CreditAttribution: ElusiveMind commentedI am wondering why this isn't handled in the switch case in Line 566. Going to investigate a bit. Can you provide your view configuration so I can do some testing?
Comment #14
ElusiveMind CreditAttribution: ElusiveMind commentedComment #15
crystaldawn CreditAttribution: crystaldawn commentedThis is the view that had the issue. I dont know why it wasnt handled previously, didnt have a whole lot of time to check into it but I did quickly find that the patch I put in fixed the issue. Whether that if clause should go there or not, I dont know, not familiar enough with the module to know. I'm also not sure why viewing the view in a different manor made the issue go away but then when its viewed a 2nd different way, it manifested itself. I know I saw this issue fixed the last time it was reported as did the client, but it popped up again so I fixed it myself with the included patch. It hasnt happened again since. This is the same view that had the original issue. I'd also note that there are still currently Ajax issues when editing the view that seem to also be related, but they dont affect actually saving the change that is made, it just pops up an ajax error. I'll see if I cant get that one pasted also.
Comment #16
crystaldawn CreditAttribution: crystaldawn commented( )
Comment #17
crystaldawn CreditAttribution: crystaldawn commentedNot sure if the above "edit view" issue is related to this title or not, I assume it is. But I get it whenever I click "Apply" on the "Header: Alpha Pagination" section. It doesnt appear to affect the view from saving any changes but it does appear to be an issue that should be fixed.
Comment #18
markhalliwellThe backtrace in #16 is the same issue caused by the above related issues; which was also fixed in #2876852: Does not work with cached views.
I'd recommend upgrading to the 7.x-2.x branch, specifically once #2870778: Use defined view fields instead of entity configuration is figured out it'll make this a little better to work with.
Comment #19
crystaldawn CreditAttribution: crystaldawn commentedI've been working with ElusiveMind who has discovered that the issue was related to something by a contributor. Not sure if you were coordinating with him or not on that, but this should be left open until his work is complete. He was busy today and only had a chance to confirm the issue, he may have more time tonight or sometime this week I would assume, to get it figured out :D I set him up with an install that allows him to reproduce the issue on command.
Comment #20
markhalliwellAs I stated above, this has been fixed (committed) in the other issue. Furthermore, there has been more progress in the 7.x-2.x branch that eliminates a lot of confusing bugs by cleaning up some of the code.
I understand that Michael has worked on this issue, but I too am very familiar with this project's codebase (I'm the other co-maintainer).
The issues you're describing above are not related to this issue, but the ones I linked above... and have since been fixed.
This issue shouldn't have been re-opened.