Advanced Search Plus Error

[newbie456]

Hi there guys. I have installed this add on and an error appeared:


1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' cd.categories_description, cd.categories_id, c.parent_id from zen_categories_d' at line 1
in:
[SELECT DISTINCT c.categories_image, cd.categories_name, , cd.categories_description, cd.categories_id, c.parent_id from zen_categories_description cd, zen_categories c where c.categories_status <> 0 AND cd.categories_id = c.categories_id and cd.language_id = '1' AND ((cd.categories_name LIKE '%lifting%' OR cd.categories_description LIKE '%lifting%') and (cd.categories_name LIKE '%magnets%' OR cd.categories_description LIKE '%magnets%') ) order by cd.categories_name]




where can I find this error to resolve it?
Any help from you guys is much appreciated.
Thanks

[newbie456]

I am using Advanced Search Plus V1.2 and zencart 1.3.9h


any help please?

thanks

[apogeerockets]

i have the same error. if i figure it out, i'll let you know.

[apogeerockets]

i have the same error. if i figure it out, i'll let you know.

Solution follows (works with zencart 1.3.9, untested in others)

In advanced_search_categories.php

replace

$select_column_list = '';

for ($col=0, $n=sizeof($column_list); $col<$n; $col++) {
  if (zen_not_null($select_column_list)) {
    $select_column_list .= ', ';
  }
  switch ($column_list_cat[$col]) {
    case 'CATEGORY_LIST_NAME':
    $select_column_list .= 'cd.categories_name';
    break;
    case 'CATEGORY_LIST_IMAGE':
    $select_column_list .= 'c.categories_image';
    break;
  }
} 

with

$select_column_list = '';

for ($col=0, $n=sizeof($column_list); $col<$n; $col++) {
  if (zen_not_null($select_column_list)) {
    $select_column_list .= '';
  }
  switch ($column_list_cat[$col]) {
    case 'CATEGORY_LIST_NAME':
    $select_column_list .= 'cd.categories_name, ';
    break;
    case 'CATEGORY_LIST_IMAGE':
    $select_column_list .= 'c.categories_image, ';
    break;
  }
} 

for some reason the original code is adding an extra comma, and thus the syntax error.


other adjustments i made:

in tpl_modules_advanced_search_categories.php i changed

$lc_text .= '<img src="images/no_picture.gif" width='.IMAGE_PRODUCT_LISTING_WIDTH.' height='.IMAGE_PRODUCT_LISTING_HEIGHT.'/></a>'; 

to

$lc_text .= '<img src="images/no_picture.gif" width='.IMAGE_PRODUCT_LISTING_WIDTH.' /></a>'; 

because my 'no image' image was getting stretched unproportionally. i also eliminated the IMAGE_PRODUCT_LISTING_HEIGHT from the line below to prevent that from stretching as well. i have all my images to be a uniform width, but don't particularly care if the height varies.

[dbltoe]

[SELECT DISTINCT c.categories_image, cd.categories_name, , cd.categories_description,

The code (by using , , ) is asking MySql to be psychic and know what it's looking for without being told. If the , , is generated by variables, the variable may have been incorrectly blanked. If not generated by variables, change , , to , and it should work.

[apogeerockets]

but now i can't get it to pop up ezpage results. *sigh*

[apogeerockets]

but now i can't get it to pop up ezpage results. *sigh*

figured this out too, thankfully.

in advanced_search_ezpages.php, comment out (or delete)

if ((EZPAGES_STATUS_HEADER == '1')  or (EZPAGES_STATUS_FOOTER == '1') or (EZPAGES_STATUS_SIDEBOX == '1')) { 

and its respective ending bracket (the last bracket on the page)

[dbltoe]

Looks like this mod has had problems with EZpages from the start.
And.... I'm not sure I would trust it with the newer versions without a lot of checking.
The mod still lists 1.3.8 even though it was upgraded after 1.3.9.
Be careful that you aren't breaking something else.

[apogeerockets]

Looks like this mod has had problems with EZpages from the start.
And.... I'm not sure I would trust it with the newer versions without a lot of checking.
The mod still lists 1.3.8 even though it was upgraded after 1.3.9.
Be careful that you aren't breaking something else.

yeah, that last work-around seems to have fixed it from what i can tell. our site isn't live yet, but i'll make sure i run more tests to make sure it didn't break it in a different way.