ozpost shipping module

[RodG]

Thanks Rod

Re: Q1

I did read that paragraph in your configuration.txt file but found it a bit strange.

Strange as in you couldn't figure out what I was attempting to state, or strange in that is behaves in this manner?

If the weight falls within the limit of a given satchel then the larger satchels should not be shown to the customer.

This is/was the OLD behaviour before the latest update. To revert to this old behaviour just select ALL satchels, and then only the relevent satchels will be shown.

Obviously the logic in the coding (either ozpost.net server side or local resolving code of the server response) can't handle the conditions as yet.

The current coding logic is correct, albeit, not 'complete'

Did you read the discussions about this change earlier in this thread?

Showing irrelevant 'options' only confuses the customer

I agree....

I am having a couple of weeks off from work and may attempt to have a crack at 'fixing' this ...

Don't be afraid to send me details of any 'fix' you come up with. I admit that I'm not entirely satisfied with the current solution to the original problem.

The original problem being that if the server determined the best satchel for the job was (for example) the 3kg XL, and is the store owner disabled this method, it could produce the situation where no valid quotes appear possible and the static rates (or no quotes at all) were being used instead.

This is/was also a tricky one to fix because it needed/needs to be done in a way that wouldn't break things for those using older client software, which is where the 'all' or 'some' idea originated from.

I know that it won't take too much more code to fix the issues now being discussed, and about the only reason why it wasn't done wih the last update was due to time constraints and the need to fix the 'hole' that had been identified, along with a much more compelling need to fix other more serious bugs with the osCommerce version of this module. In short, this current code is a little bit of a compromise between not giving a quote at all vs giving too many quotes, some of which are unnessesary.

In summary, I agree that it currently isn't as nice as it could be, so if you do come up with a fix before I do I'll happily consider adding it to future updates. Howver, before you spend too much time on it, please be aware that I've *just* released ozpost for opencart, which means I now have time to start back with zencart code again, and this is going to be my #1 priority.

Cheers
Rod

[frank18]

This is/was the OLD behaviour before the latest update. To revert to this old behaviour just select ALL satchels, and then only the relevent satchels will be shown.

That did work - but: I don't want to offer 500gm Regular and 3Kg Regular which means that I am not selecting ALL satchels. That's the 'strange' part ...

Don't be afraid to send me details of any 'fix' you come up with. I admit that I'm not entirely satisfied with the current solution to the original problem.

The original problem being that if the server determined the best satchel for the job was (for example) the 3kg XL, and is the store owner disabled this method, it could produce the situation where no valid quotes appear possible and the static rates (or no quotes at all) were being used instead.

This is/was also a tricky one to fix because it needed/needs to be done in a way that wouldn't break things for those using older client software, which is where the 'all' or 'some' idea originated from.

I know that it won't take too much more code to fix the issues now being discussed, and about the only reason why it wasn't done wih the last update was due to time constraints and the need to fix the 'hole' that had been identified, along with a much more compelling need to fix other more serious bugs with the osCommerce version of this module. In short, this current code is a little bit of a compromise between not giving a quote at all vs giving too many quotes, some of which are unnessesary.

In summary, I agree that it currently isn't as nice as it could be, so if you do come up with a fix before I do I'll happily consider adding it to future updates. Howver, before you spend too much time on it, please be aware that I've *just* released ozpost for opencart, which means I now have time to start back with zencart code again, and this is going to be my #1 priority.

Cheers
Rod

Got that - in principle your mod is an absolute marvel, top idea. But I also understand that it is quite complex to code. And - like us humans - nothing is absolutely perfect.

I have subscribed to email notifications about changes of this thread and will keep my ears/eyes glued to updates.

Cheers again and have a nice weekend

Frank

[RodG]

That did work - but: I don't want to offer 500gm Regular and 3Kg Regular which means that I am not selecting ALL satchels. That's the 'strange' part ...

Not so strange really.... by not having ALL selected in your client settings is telling the server that you wish to filter the satchels to use locally, which means the server will provide quotes for *all* satchels (else there won't be anything to filter locally).

If you tell the client that you will handle ALL satchels sets the condition whereby only the most suitlable satchel size is returned by the server..

By design, the server *should* only output viable methods, which means only one satchel size at any given time.

I've needed to break this design rule because of the aforementioned problems,

A little confusing perhaps, but not what I would call 'strange'.

Then again, I have very odd ideas as to what is or isn't strange in this confusing world of ours :-)

Cheers
Rod