Evening all,

So if there a problem with the module ? It's been a long time and I saw that it was maintained well. One thing woud have been easier though. When I wrote it and then left, I was in the process of working by increment, so that the SQL calculations for postage say for "signed for" could be worked out as "first class weight + 0.98 pence" or whatever the current value is, then when the rates changed there would be a "base set of values" say from April 2008 and all the installation program would do is go, right we're now on version XXX so we need to split the stored values by : and comma loop through them and add 19 pence. There would be special cases for exampled when 21p is added rather than 22p, but a few sql statements was a lot easier than manually having to add each value (because I did it about 17 times and it's an onerous task).

So who's in charge now and what's the problem ? If the data is being posted out to one payment method, but not to another, the best thing would be to dump the data in the payment module causing the problem and work out if it is actually still there, or being lost on Google's side of the net.

Regards.
Philip