Is anyone using Biblio as well as the Support Ticketing module?
When I give a role to a user that allows them to submit support tickets the Biblio module stops working. They get 'The website encountered an unexpected error. Please try again later.'
And in the and in the log messages I get:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'bc.uid' in 'where clause': SELECT bc.*, bcd.* FROM {biblio_contributor} bc INNER JOIN {biblio_contributor_data} bcd ON bcd.cid = bc.cid LEFT OUTER JOIN {support_ticket} st ON st.nid = bc.nid WHERE (bc.vid IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2, :db_condition_placeholder_3, :db_condition_placeholder_4, :db_condition_placeholder_5, :db_condition_placeholder_6, :db_condition_placeholder_7, :db_condition_placeholder_8, :db_condition_placeholder_9, :db_condition_placeholder_10, :db_condition_placeholder_11, :db_condition_placeholder_12, :db_condition_placeholder_13, :db_condition_placeholder_14, :db_condition_placeholder_15, :db_condition_placeholder_16, :db_condition_placeholder_17, :db_condition_placeholder_18, :db_condition_placeholder_19, :db_condition_placeholder_20, :db_condition_placeholder_21, :db_condition_placeholder_22, :db_condition_placeholder_23, :db_condition_placeholder_24)) AND(( (st.client IN (:db_condition_placeholder_25)) AND (bc.uid = :db_condition_placeholder_26) )OR (st.client IS NULL ) ) ORDER BY bc.vid ASC, bc.rank ASC; Array ( [:db_condition_placeholder_0] => 59 [:db_condition_placeholder_1] => 60 [:db_condition_placeholder_2] => 61 [:db_condition_placeholder_3] => 62 [:db_condition_placeholder_4] => 65 [:db_condition_placeholder_5] => 71 [:db_condition_placeholder_6] => 72 [:db_condition_placeholder_7] => 73 [:db_condition_placeholder_8] => 76 [:db_condition_placeholder_9] => 77 [:db_condition_placeholder_10] => 79 [:db_condition_placeholder_11] => 80 [:db_condition_placeholder_12] => 81 [:db_condition_placeholder_13] => 82 [:db_condition_placeholder_14] => 83 [:db_condition_placeholder_15] => 84 [:db_condition_placeholder_16] => 85 [:db_condition_placeholder_17] => 86 [:db_condition_placeholder_18] => 87 [:db_condition_placeholder_19] => 88 [:db_condition_placeholder_20] => 89 [:db_condition_placeholder_21] => 90 [:db_condition_placeholder_22] => 92 [:db_condition_placeholder_23] => 93 [:db_condition_placeholder_24] => 105 [:db_condition_placeholder_25] => 2 [:db_condition_placeholder_26] => 10 ) in biblio_load_contributors_multiple() (line 75 of /home/sltru/public_html/data/sites/all/modules/biblio/includes/biblio.contributors.inc).

Has anyone got any ideas??
If I remove the Support Ticket Role it all works again.
I had some feedback from the Biblio module developer:

I believe that the issue lies in the Support module in the function

support_query_alter(QueryAlterableInterface $query)

The biblio_contributor query is tagged with 'node_access' and the above mentioned hook is messing it up when I don't think there is any need for the support module to be altering this particular query.

I would like to use the Support Module but am unable to because of this problem.
Many Thanks
Julie

Comments

somatics’s picture

somatics commented

This issue is happening with many modules other than just Biblio. I'm having the issue with forums, with views with Taxonomy Depth contexts, and it appears in several other places. I have seen multiple posts about this same error from Support Ticket when using the Book module as well.

My issue about this is at http://drupal.org/node/1376120

auraell’s picture

auraell commented

I am having same issue

somatics’s picture

somatics commented

What I found by looking around the web a bit is that this conflict is apparently happening with Support Ticket plus many other modules. I found several other modules that post this bug with Support Ticket. Like this issue thread, none of them have gotten a response yet.

My only solution, after waiting a while for a reply, and after months of customers coming to rely on our Support Ticket feature, was to simply disable the whole Support Ticket package entirely.

jward50’s picture

jward50 commented

I came to the same conclusion, disable the module.

mattbk’s picture

mattbk commented

This happens for me as well (with STS and Biblio), but only when I'm not logged in.

EDIT:
Additional information: I get this error when viewing the front page (which includes a View holding Biblio information) as an Anonymous user (not logged in). When I log in, the error does not occur.

Using current dev version of Support and Biblio RC3.

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'bc.uid' in 'where clause': SELECT bc.*, bcd.* FROM {biblio_contributor} bc INNER JOIN {biblio_contributor_data} bcd ON bcd.cid = bc.cid LEFT OUTER JOIN {support_ticket} st ON st.nid = bc.nid WHERE (bc.vid = :db_condition_placeholder_0) AND(( (st.client IN (:db_condition_placeholder_1)) AND (bc.uid = :db_condition_placeholder_2) )OR (st.client IS NULL ) ) ORDER BY bc.vid ASC, bc.rank ASC; Array ( [:db_condition_placeholder_0] => 3760 [:db_condition_placeholder_1] => 1 [:db_condition_placeholder_2] => 0 ) in biblio_load_contributors_multiple() (line 75 of /var/www/sites/all/modules/biblio/includes/biblio.contributors.inc).

MY SOLUTION: I was able to remove this issue by removing the permissions to 1) create support tickets and 2) view support tickets by Anonymous (not logged in) users. Keep in mind that there are currently TWO sets of permissions for Support: the first is for the node/content type, the second is for the Support module itself (just reported at #1458904: Some permissions seem duplicated, which may be confusing for some users.).

This may not be an ideal solution for everyone; in our case it's actually more secure to have the tickets hidden from view.

jeremy’s picture

jeremy commented
Status: Active » Closed (duplicate)

Duplicate, hopefully resolved with this commit in another ticket:
#1376120: Support Ticket is inserting query requests in our Views -- and breaking the Views!