paypal order comfirmation uses old order nr

Hi i have a problem.

When you do a paypal payment, i receive the order in my admin and in my e-mailbox. For example order 300 ( which is correct)

But the order confirmation is saying it is order 275 ( which is not correct as this is an old order which has already been processed and delivered)

What is going wrong and how can i change this so my order number in admin and the order number with the confirmation are the same.

the straneg thing is, that the order comfirmation that the client gets is with the correct order number 300 . So only the confirmation on the website is stuck on nr 275

Thanks.

Ilonka

oke i solved some of the problems.

so now it is as follows:

place an order , pay with paypal get a confirmation with the correct order number. ( jippie it works )

go to admin/customers/paypal ipn and i see all the paypal payments ( jippie this works also )

go to admin home click on the order click the green edit button and there we have the error:

1054 Unknown column 'zen_order_id' in 'where clause'
in:
[select * from paypal where zen_order_id = '223' order by paypal_ipn_id DESC LIMIT 1]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

This error can be solved my doing the following SQL patch

ALTER TABLE paypal CHANGE order_id zen_order_id int(11) unsigned NOT NULL default '0';

But this is the bug that stops the order counting at the website confirmation.

How can i alter the SQL patch above so it will not stop the order counting but does show me the details per payment. ( as there are more details shown per payment )

Thanks for your help.

ilonka:

1054 Unknown column 'zen_order_id' in 'where clause'Changing the database to get rid of the error message will not solve your problem.

The only reason for the database not matching what the code is asking for ... is if you're using mismatched versions of code.

v1.3.8 changed the paypal table structure. If you're using v1.3.8 code on a v1.3.7.x or earlier database, or using v1.3.7.x or earlier code on a 1.3.8 database, you're going to encounter this error.

The real solution is to make sure any code you've changed, installed, or upgraded, is all the same version.