weird SQL error on account_history.php

[tomfilepp]

so i'm getting this error on my account_history.php page. it's on an account with no previous orders on it. i haven't tried with an account with orders, as i'm still in production.

 

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 '-10, 10' at line 1

 

select o.orders_id, o.date_purchased, o.delivery_name, o.billing_name, ot.text as order_total, s.orders_status_name from orders o, orders_total ot, orders_status s where o.customers_id = '2' and o.orders_id = ot.orders_id and ot.class = 'ot_total' and o.orders_status = s.orders_status_id and s.language_id = '1' order by orders_id DESC limit -10, 10

 

any ideas?

[jdvb]

there is an update for that in the last release I thought.

that error is displayed only when there is no order history.

[crash3903]

try

 

edit /includes/classes/split_page_results.php

 

find

 

$this->sql_query .= " limit " . $offset . ", " . $this->number_of_rows_per_page;

 

 

(about line 66)

 

insert before it

 

if($offset <0 ) $offset = 0;

 

 

 

the same in admin//includes/classes/split_page_results.php

[tomfilepp]

that worked like a charm, thank you. it shows 0 of 0 results now. the only thing that is a little strange is, it shows pagination links anyway, even though there are 0 results. and the pagination numbers are negatives:

 

Result Pages: -4 -3 -2 -1 0

 

each of those links to another 0 of 0 results page.

 

try

 

edit /includes/classes/split_page_results.php

 

find

 

$this->sql_query .= " limit " . $offset . ", " . $this->number_of_rows_per_page;

(about line 66)

 

insert before it

 

if($offset <0 ) $offset = 0;

the same in admin//includes/classes/split_page_results.php

[Guest]

Also wanted to post a quick thank-you for this fix, I have a client with this exact issue and the fix came right up on a search. Bless ya'! I'd have been beating my head against this all day otherwise. :'(

 

:D Bailey

[crash3903]

Also wanted to post a quick thank-you for this fix, I have a client with this exact issue and the fix came right up on a search. Bless ya'! I'd have been beating my head against this all day otherwise. :'(

 

:D Bailey

 

your welcome :)