After update to 1.8 I'm unable to create content...

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'T.name' in 'on clause': SELECT Q.name AS name, Q.title AS title FROM {nodequeue_queue} Q INNER JOIN {nodequeue_types} T ON Q.name = T.name AND T.type = :type; Array ( [:type] => page ) in _auto_nodequeue_get_qids() (line 145 of /mnt/stor9-wc2-dfw1/484947/870851/www.meridianhomecare.info/web/content/sites/all/modules/auto_nodequeue/a...).

CommentFileSizeAuthor
#4 auto_nodequeue_column_not_found-2315955-4.patch333 bytesdevd

Comments

labboy0276’s picture

labboy0276 commented

+1

I am too seeing this happen as well since upgrading the other day

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'T.name' in 'on clause': SELECT Q.name AS name, Q.title AS title FROM {nodequeue_queue} Q INNER JOIN {nodequeue_types} T ON Q.name = T.name AND T.type = :type; Array ( [:type] => audio ) in _auto_nodequeue_get_qids() (line 145 of /srv/bindings/9823a18e319a42a08b8a53302051a07f/code/sites/all/modules/contrib/auto_nodequeue/auto_nodequeue.module).

maustyle’s picture

maustyle commented

same here

devd’s picture

devd commented

Hi All,

This is the compatibality issue.
Please use this module as with nodequeue versions

auto_nodequeue-7.x-1.8 nodequeue-7.x-3.x-dev
auto_nodequeue-7.x-1.6 nodequeue-7.x-2.0-beta1

devd’s picture

devd commented
StatusFileSize
new auto_nodequeue_column_not_found-2315955-4.patch333 bytes

Hi davidfells,

This issues is occuring due to compatibality with nodeque version7.x-3.x.
If it is working fine and you are going to apply this patch.
Please write git commit message like as:

git commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]." --author="dev.firoza "

Also please apply the Enable automated testing on your module. So we applied patches can be verified by automated system cron.

davidfells81@gmail.com’s picture

davidfells81@gmail.com commented

devendra I'm going to add you as a comaintainer, I really don't have time to stay on top of this.

devd’s picture

devd commented
Version: 7.x-1.8 » 7.x-1.9
Status: Active » Closed (fixed)

Fixed.

Now auto_nodequeue7.x-1.9 will work with nodequeue7.x-3.x or upper versions.

joshuautley’s picture

joshuautley commented

devendra,

I think you should change the version of this fix to 3.x to match the dev branch of nodequeque.

This will eliminate confusion for people who are simply keeping there module versions up-to-date. requiring version 1.6 to update to 1.9 doesn't make sense since v1.9 requires a module in dev which is not recommended on prod sites.

This is how its done for other modules (image field and file field for example have always kept current with each others relative versions).

So, Node Auto Que 7.x-3.0 for Nodequeue 7.x-3.x-dev

As should be Node Auto Que 7.x-2.0 for Nodequeue 7.x-2.0-beta1

Make sense?

scsmith_calarts’s picture

scsmith_calarts commented

I have this error too. I'm using Nodequeue 7.x-2.0-beta1, so I downgraded back to 1.6, but I'm still getting the "Object not found" error. Any suggestions?

rajeevgole’s picture

rajeevgole
He/Him
Primary language English
commented

I am using Auto Nodequeue(7.x-2.1) with Nodequeue(7.x-2.0-beta1). When i create a node then it show the below message.

Notice: Undefined property: stdClass::$original_queues in auto_nodequeue_node_update() (line 156 of /auto_nodequeue/auto_nodequeue.module).

rajmataj’s picture

rajmataj commented

I too am using Auto Nodequeue(7.x-2.1) with Nodequeue(7.x-2.0-beta1) and couldn't even log in via the web interface because of this error. Fortunately, I have Drush installed on the remote server where the website resides and I disabled auto_nodequeue drush dis auto_nodequeue which allowed me to login at least. I ran the update database command again, and so far so good, however I will not be enabling auto_nodequeue until a compatible update to Nodequeue is released.