Hello,
I am getting an error message when I enable Nodequeue. I've searched the web and haven't found anything that has worked out. Please advise. Any help or suggestions are appreciated greatly.
PDOException: SQLSTATE[42000]: [Microsoft][SQL Server Native Client 11.0][SQL Server]Column 'nodequeue_queue.name' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.: SELECT q.*, COUNT(s.sqid) AS subqueues FROM {nodequeue_queue} q LEFT JOIN {nodequeue_subqueue} s ON q.qid = s.qid WHERE q.qid IN (:to_load_0, :to_load_1) GROUP BY q.qid; Array ( [:to_load_0] => 1 [:to_load_1] => 2 ) in nodequeue_load_queues() (line 615 ofE:\dev\sites\all\modules\contrib\nodequeue\nodequeue.module).
Comments
Comment #1
kcoonce CreditAttribution: kcoonce commentedUpdate:
Through some research I found an article where someone said it was an issue from moving to 7.x-2.x to 7.x-3. I uninstalled NodeQueue AND deleted the colums in the SQL database. After that I installed 7.x-3.x because the article I read said 7.x-3.x removes that column. I am now getting a separate error message.
The new error message reads
PDOException: SQLSTATE[42S02]: [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'nodequeue_queue'.: SELECT nq.[qid] AS [qid], nq.[name] AS [name] FROM {nodequeue_queue} nq; Array ( ) in nodequeue_update_7300() (line 417 of E:\dev\sites\all\modules\contrib\nodequeue\nodequeue.install).
Once again, all and any help is greatly appreciated.
Comment #2
megan_m CreditAttribution: megan_m commentedLong story short: Use the 2.x-dev version.
I got the same error when I installed a Feature with exported Nodequeues implemented using Features Extra on IIS using MS SQL Server. The error happened right away when I enabled the feature. Then I tried uninstalling the Feature, Features Extra, and Nodequeue, then re-installing Nodequeue on its own. This worked fine, but the error came up again when I tried creating a simple queue. This was using Nodequeue 7.x-2.0-beta1.
It seems that SQL Server has a problem with the database query on line 615:
This line has been changed in the 2.x-dev branch to remove the GROUP BY clause, which solves the issue.
This Stack Overflow question may have some insight into why this happened:
http://stackoverflow.com/questions/13999817/reason-for-column-is-invalid...
The second issue with 7.x-3 looks to be a different problem.