So, I have a Geo Zone for Ohio set. Then I have the Tax Rate setup. Then the products ALL have "Ohio Tax" (the name of the rule) set. A guy in New York just ordered, and it actually charged HIM tax where it is not supposed to... messed with it and I cannot get it to stop that. Any ideas?
I think I figured it out... My test users were both in Ohio... /facepalm
Still not sure why it figured the tax for the real customer in NY though... I'll have to wait and see what happens but it does look all right. here's to hoping! Thanks!
Version?
This may lead to a Bingo: "My test users were both in Ohio" but "it figured the tax for the real customer in NY" seems to mean that the database itself is the problem. At this juncture version matters.
The install/upgrade script in 1.5.6.0 was modified some time ago but seems not to have been (re)run in the majority of installations, and the one in 1.5.6.1 might well be good as-is but a bare few numbered mysql errors have sprouted. Go into phpMyAdmin and first Export a backup. Then look at the table(s) affected, and see whether there is anything at all goofy in the grid layout, just visually check all of it for proper alignment of columns and rows, without any offsets of some rows into segments jutting to the right beyond normal right marginal bounds. Offsets of that kind can occur in recent as well as in older OC, and in instances I've seen there are bouts of offsets with intervening bouts of normal records -- records jutting out on the right, records okay, more of former, more of latter, etc., perhaps two to five records per bout. If none, then go to bottom left in main pane, Select All of the tables, and ask Check tables, then see whether all are listed OK. If yes, stop. If not, Select All of the tables, and ask Repair tables, then see whether all are listed OK. If yes, stop. If not, see what you have set aside in phpMyAdmin / Export or host .zip Backups in order to use it instead. If none, then you can open the fresh backup and fix it by hand. If you do that be absolutely certain that all piddly teensy nuances of syntax remain intact, such as backticks, one ; per and ending each record line, etc.. Doing that will keep you out of mischief for a little while.
This may lead to a Bingo: "My test users were both in Ohio" but "it figured the tax for the real customer in NY" seems to mean that the database itself is the problem. At this juncture version matters.
The install/upgrade script in 1.5.6.0 was modified some time ago but seems not to have been (re)run in the majority of installations, and the one in 1.5.6.1 might well be good as-is but a bare few numbered mysql errors have sprouted. Go into phpMyAdmin and first Export a backup. Then look at the table(s) affected, and see whether there is anything at all goofy in the grid layout, just visually check all of it for proper alignment of columns and rows, without any offsets of some rows into segments jutting to the right beyond normal right marginal bounds. Offsets of that kind can occur in recent as well as in older OC, and in instances I've seen there are bouts of offsets with intervening bouts of normal records -- records jutting out on the right, records okay, more of former, more of latter, etc., perhaps two to five records per bout. If none, then go to bottom left in main pane, Select All of the tables, and ask Check tables, then see whether all are listed OK. If yes, stop. If not, Select All of the tables, and ask Repair tables, then see whether all are listed OK. If yes, stop. If not, see what you have set aside in phpMyAdmin / Export or host .zip Backups in order to use it instead. If none, then you can open the fresh backup and fix it by hand. If you do that be absolutely certain that all piddly teensy nuances of syntax remain intact, such as backticks, one ; per and ending each record line, etc.. Doing that will keep you out of mischief for a little while.
Who is online
Users browsing this forum: No registered users and 35 guests
