Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

UPGRADING FROM ONE SNAPSHOT TO ANOTHER


hostmedia

Recommended Posts

I have a snapshot from November 2002 which I have managed to tweak

to the point where everything is exactly how I want it.

 

The only thing I need now is to get my authorize.net to work on it.

I have tried the mods and it is not working for me.

 

Since recent snapshots have the new AIM/SIM authorize.net in

it, I will like to upgrade to the most recent snapshot.

 

Can anyone tell me how to upgrade while keeping all my current

settings.

 

Steve.

Link to comment
Share on other sites

Steve,

 

I just finished fixing my authorize.net credit card module of a few quirks.

 

1) On the checkout page, it said "authorize.net" as the option for credit cards. This was somewhat confusing to me, and I can only imagine what customers were thinking. I changed it to read: "Credit Card". This only causes a bit of confusion when you go to admin because you have a Generic credit card option and an authorize.net option (which now reads credit card). I can keep it striaght!

 

2) Credit Card Expiry Date? I was able to fix this as well. It now reads: Credit Card Expiration Date.

 

 

BACK UP YOUR FILES!!!!!

Both of these can be fixed by going to the catalog/includes/languages/english/modules/payment folder and opening the file called authorize.net. On line 13 change 'Authorize.net' to 'Credit Cards'. On line 18 change 'credit card expiry date' to "Credit Card Expiration Date'.

 

 

The next problem I solved was an Issue with authorize.net

 

Recently, there was a change in the Simple Integration Method (SIM) protocol. I downloaded my OSC 2.2 snapshot around Dec 13, 2002. I have spent the past 2 months building and modifying the site. I was trying to go to a live test for credit card processing, when I discovered I could not communicate with authorize.net. I checked out the forums here, and discovered a Transaction Key is now needed. My snapshot did not contain a transaction key field. Rather than delete all my hard work, and start over, I decided to try to figure out which files would control that function, and replace them.

I figured it out.

 

 

BACK UP YOUR FILES!!!!!

I replaced the following files of my Dec 13, 2002 snapshot with the same files of a Feb13, 2003 snapshot.

 

 

1) catalog/includes/modules/payment/authorize.net.php

 

2) catalog/checkout_process.php

 

3) catalog/admin/modules.php

 

4) catalog/admin/includes/functions/general.php

 

I am not completely sure if all of these files need to be replaced. I changed the 4 files, then went to admin to test it. Maybe only 2 or 3 are needed.

 

NOTE: Before you replace these files, you really should turn OFF the authorize.net module in admin. When you are done replacing the files, turn the module back on, enter your user name transaction key, etc, and you should be in business.

After replacing these files, the admin module now prompts me for a transaction key. I have tested the credit card module, and it works!!

Link to comment
Share on other sites

Mark,

You did it. I can taste it now.

I followed everything you wrote above

to the letter.

 

(1) My test order made it to authorize.net

(2)the order was approved.

(3)The receipts were sent.

 

I even tried with "production mode" and it worked again.

 

However, The following is the message I got

in what should have been the order success page.

 

For some reason, it didn't make it back to OSC after the approval.

So the "order process e-mail" was not sent.

******************************************************

This is the error after the payment was approved on:

https://secure.authorize.net/gateway/transact.dll

 

 

1054 - Unknown column 'orders_status_id' in 'field list'

 

insert into orders_status_history (orders_id, orders_status_id, date_added, customer_notified, comments) values ('4', '', now(), '1', '')

 

[TEP STOP]

 

I am excited because I feel I am close. All need now is to figure

why I got that error on:

https://secure.authorize.net/gateway/transact.dll

 

Any help here will be very appreciated.

 

Thanks

Steve

Link to comment
Share on other sites

Steve,

 

 

Did you happen to use the 2.2 MS1 snapshot to get your files from? The reason I ask is..I am updating to the MS1 myself tonight, and I just got the same exact error you are getting. Let me know if this is the case. I think I have a solution for us both.

 

 

Mark

Link to comment
Share on other sites

Hmmm... It would appear I have solved this problem. I have not had time to look all the way through this, but I will suggest a temporary fix:

 

 

I will e-mail you those 4 files I have from my previous cart. Most likely you will not have any trouble. I would STRONGLY suggest that you keep the backups that you made of your ORIGINAL files. Keep them until you are satisfied that you do not need them anymore (pronounced forever :wink: )

 

You will get an e-mail with the following:

 

authorizenet.php = catalog/includes/modules/payment/authorizenet.php

 

checkout_process.php = catalog/checkoutprocess.php

 

modules.php = catalog/admin/modules.php

 

general.php = catalog/admin/includes/functions/general.php

 

 

 

Give me a few minutes, and I will e-mail them to you. Let me know how it works. :)

 

 

Mark

Link to comment
Share on other sites

  • 3 weeks later...

I did not make any changes. I had the files left over from an upgrade that I did a few weeks back. All you have to do is replce the new files with the older files and viola!

 

 

Mark

Link to comment
Share on other sites

Well, I need to make the switch for Authorize.net however I have made so many mods that I don't want to upgrade and redo all of this. That's why I was asking what changes you made to get it up and going.

 

Thanks!

Link to comment
Share on other sites

I just finished fixing my authorize.net credit card module of a few quirks.  

 

1) On the checkout page, it said "authorize.net" as the option for credit cards. This was somewhat confusing to me, and I can only imagine what customers were thinking. I changed it to read: "Credit Card". This only causes a bit of confusion when you go to admin because you have a Generic credit card option and an authorize.net option (which now reads credit card). I can keep it striaght!  

 

2) Credit Card Expiry Date? I was able to fix this as well. It now reads: Credit Card Expiration Date.  

 

 

BACK UP YOUR FILES!!!!!  

Both of these can be fixed by going to the catalog/includes/languages/english/modules/payment folder and opening the file called authorize.net. On line 13 change 'Authorize.net' to 'Credit Cards'. On line 18 change 'credit card expiry date' to "Credit Card Expiration Date'.  

 

 

The next problem I solved was an Issue with authorize.net  

 

Recently, there was a change in the Simple Integration Method (SIM) protocol. I downloaded my OSC 2.2 snapshot around Dec 13, 2002. I have spent the past 2 months building and modifying the site. I was trying to go to a live test for credit card processing, when I discovered I could not communicate with authorize.net. I checked out the forums here, and discovered a Transaction Key is now needed. My snapshot did not contain a transaction key field. Rather than delete all my hard work, and start over, I decided to try to figure out which files would control that function, and replace them.  

I figured it out.  

 

 

BACK UP YOUR FILES!!!!!  

I replaced the following files of my Dec 13, 2002 snapshot with the same files of a Feb13, 2003 snapshot.  

 

 

1) catalog/includes/modules/payment/authorize.net.php  

 

2) catalog/checkout_process.php  

 

3) catalog/admin/modules.php  

 

4) catalog/admin/includes/functions/general.php  

 

I am not completely sure if all of these files need to be replaced. I changed the 4 files, then went to admin to test it. Maybe only 2 or 3 are needed.  

 

NOTE: Before you replace these files, you really should turn OFF the authorize.net module in admin. When you are done replacing the files, turn the module back on, enter your user name transaction key, etc, and you should be in business.  

After replacing these files, the admin module now prompts me for a transaction key. I have tested the credit card module, and it works!!

 

 

If you follow these instructions it should fix your problem. If you do not have the files from a pre-MS1 snapshot, you will have to update your mysql tables slightly. If you do not wish to change the tables, you can e-mail me and I can send you the files that go with a pre MS1 snapshot that will work without updating the mysql tables.

 

Thanks!

 

Mark

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...