Posted by faskone on February 6, 2008 at 9:46am
Hello,
I have a problems with ecommerce-5.x-3.4. I install this module and the payment gateway for la caixa (Spanish bank). I configure the payment gateway but when go to checkout, a page says that i need the i18n_language() function that is in the i18n module.
Then I install this module, and the payment gateway work fine. But in the ecommerce section, i have and error when i click into E-Commerce -> Products. This error is:
* user warning: Unknown column 'n.nid' in 'on clause' query: SELECT COUNT(*) FROM node as n, ec_product as p LEFT JOIN i18n_node i18n ON n.nid = i18n.nid WHERE (i18n.language ='es' OR i18n.language ='' OR i18n.language IS NULL) AND ( n.vid = p.vid AND n.status = 1 ) in /var/www/portal/includes/database.mysql.inc on line 172.
* user warning: Unknown column 'n.nid' in 'on clause' query: SELECT n.nid, n.title, p.* FROM node as n, ec_product as p LEFT JOIN i18n_node i18n ON n.nid = i18n.nid WHERE (i18n.language ='es' OR i18n.language ='' OR i18n.language IS NULL) AND ( n.vid = p.vid AND n.status = 1 ) ORDER BY p.nid ASC LIMIT 0, 50 in /var/www/portal/includes/database.mysql.inc on line 172.
I find in the forums that in the version ec4 this problem is fix, but with this versión de payment gatewy don't work.
I need to solve this problem, can anyone help me?
Excuse for my english, thats no my native language. Thanks for all
Categories: help, i18n problems, payment gateway
Comments
replace
replace this:
ecommerce/product/product_overview:1120
$sql = 'SELECT n.nid, n.title, p.* FROM {node} as n, {ec_product} as p WHERE n.vid = p.vid AND n.status = 1'. tablesort_sql($header);
on this way:
$sql = 'SELECT n.nid, n.title, p.* FROM {ec_product} as p, {node} as n WHERE n.vid = p.vid AND n.status = 1'. tablesort_sql($header);
Thank you very much!!!!
Thanks for the reply, we need this to work fine a ecommerce.
Albert
thanks - solve my issue too
Had same issue and this solved my issue to (thank you) ,
this is the same even at 5.3.5 version,
I have tried to look at the issue queue and there wasn't any patch for this issue,
is this a known issue ?