Quote Originally Posted by gmturner View Post
But when the customer specifically enters and different suburb why doesnt it use that?
It would be easier to ask 'when will this functionality be added'?, because the answer would be 'The next release following the first reported incident of it being an actual problem'

OK, now the long answer:
One of the aims of any code I develop is to keep it is simple and as foolproof as possible, so, with this in mind, the first renditions of ozpost only supported Australia Post rates, and since AP base their prices entirely on their postcodes it made no sense for the ozpost module to gather the suburb information. In fact, the modified ozpost template file was created specifically to remove the then superflious dropdown menu(s)

Of the other Couriers, the first of which was added earlier this year, some need postcode only, some need suburb only, and the remaining requires both a suburb and a postcode. Anyway, it has only been 'recently' that the 'need' for suburb names has emerged, and you are the first to report it as being an 'actual' problem rather then a theoretical problem.

This is/was important for me to know, because the act of re-introducing what are essentially 'user inputted' suburb names raises what could be bigger concerns due to suburb names not matching the 'official' names because of mis-spelling, upper/lower case differences, abbreviations ("McKoy" vs "McKoy" vs "Macoy", etc)

This also requires more input validation, and decisions on how to behave on non fatal errors, eg, user inputs postcode "1234" and Suburb "St Ives", and the 'official' suburb name is "Saint Ives", but the first official name for the postcode '1234' is 'Devils advocate' - Should the module return an error (invalid suburb) or the quote to Devils advocate? Does this need to be a user selectable option? (so much for KISS)

Anyway, as I said, that's the long answer. The short answer is probably more to your liking. :-)

Cheers
Rod