For further information, please refer to this thread: http://www.zen-cart.com/forum/showth...light=austpost
Cheers
GAM
For further information, please refer to this thread: http://www.zen-cart.com/forum/showth...light=austpost
Cheers
GAM
Further to this problem, if the failue of the Estimate Shipping and Checkout pages are indeed a result of the AustPost DRC sever being down, surely the austpost.php code can be modified to indicate this in these pages allow the pages to continue to function? As it is now, this occurence disables these pages and renders the store unavailable for estimates and checkout.
A notification to the customer along the following lines would be good:
'The Australia Post rates server is currently unvailable, as such we cannot provide shipping estimates or costs for Australia Post services at this time. This problem should be corrected soon. If these services are required, we ask you to please check back again soon.
We apologise for any inconvenience.'
RodG, what do you think, is it easy enough to implement? (Obviously, I'm hoping you're around and will see this ;))
Cheers
GAM
Hi GAM,
> RodG, what do you think, is it easy enough to implement?
Unfortunatetly, no, it isn't easy to implement. The reason being is that the zencart core code traps connectivity issues and aborts the processing without returning back to the AP module, so the AP module never gets a chance to produce custom error messages.
This is also why those people that have problem using the file method need to manually modify the code to use the CURL method. Ideally, if one method fails it would be nice to have it automatically try the other, but this doesn't seem easily possible either.
Cheers
Rod
I vaugely remember something about the 611 errors, it has something to do with the way php is configured on your server. You need to change the way that the module does something by editing out a comment in a file, something about file sessions to curl$() or something.
Anyway I tried to go to the link in that other thread and it appears as though the AUST POST DRC server is having issues again.
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://drc.edeliver.com.au/ratecalc.asp?
The following error was encountered:
The system returned:
- Connection Failed
(110) Connection timed out The remote host or network may be down. Please try the request again.
Your cache administrator is root.
Speeeeeewin'!!!!!!!!!!!!!!!!!!!!!!!!
This module was looking like the most fantastic thing, but if the DRC server keeps going down and stopping my shops from working well that just (insert expletive here)!!
I'm not unhappy with the module at all let me make that clear, but if Australia Post keeps preventing my customers from using the checkout, I will have no choice but to not use this module and do something lame like flat rate shipping.
DAVE
:)
In Australia Post's and AustPosts module's defence, according to my logs, the last time this occured was 8-Aug-2007 (3months). Every so often is not bad as long as it doesn't take long to recover.
Personally I think the module is great too... needs some more enhancements and little fixes, but well worthy of installation and use if it suits your site and business operation.
Cheers
GAM
ps. I've been intently working on packaging sizes and getting all my product dimensions accurate and up to date however I'm pretty sure that there are still some issues with the 'letter size' options and something weird with small dimensions submitted to the DRC. I'm investigating and will report back with my prognosis ;)
I'm also working on some simple, rather long winded, but better methods for 'bin-packing' than the straight 'stack by height' method that it currently uses.
Hi Gam,
> I've been intently working on packaging sizes and getting
> all my product dimensions accurate and up to date however
> I'm pretty sure that there are still some issues with the 'letter size' > options and something weird with small dimensions submitted to
> the DRC. I'm investigating and will report back with my prognosis ;)
I can save you a bit of time .... yes, there are some issues with letter sized items and parcels with small dimensions. If I recall correctly (its been a few months) but under the right (wrong?) conditions, some 'packages' may end up being too large/heavy to be classed as a letter, yet too small to be classed as a 'parcel', so errors or unexpected quotes will occur.
The fix is pretty simple (I've actually got a fixed version sitting in the wings), it basically involves adding a check to ensure that if a 'package' happens to fall into this category new default dimensions are applied to ensure the minimum requirements are met.
Cheers
Rod
I'm not in test mode just at the moment because I accidently imported product details that were 3 months old and have the site 'down for maintenance'... backup will be restored later.
Anyway, the issues I was experiencing are:
1. Parcel quoted when weight and dimensions < Large Letter maximums.
2. iirc, a single item <9cm x 9cm x 1.5cm returns 'at least one dimension is invalid' and also, iirc, > above but < max. letter returns '...max. girth exceeded...' or similar error msg.
3. Specifying the mentioned 50mm x 50mm x 30mm didn't work either.
I looked at tricking the 'stack' method by specifying 0.5cm and 9x9cm so that it would accept Large Letter for 4x product of this size. It didn't work, iirc, max girth msg.
I believe these are DRC errors and not AustPost, is this right?
When I was looking at the code, I imagine a possible simple fix along the lines of... if AustPost (module) determines that dimensions (and weight) are within Large Letter max dimensions, submit Large Letter max dims to DRC for quote on weight/destination.
Another possible workaround I am considering is to specify the Default Parcel Size as max letter i.e., 23x36x2 (or whatever it is) then rely on all my products having accurate dimensions to ensure 'Parcel' rates when the default parcel is exceeded.
As you might relise, Large Letter size is important for my store so I am keen to get a working solution.
Also, if you can explain or point me in the right direction on how to enable/disable debugging this would be a great help as I would like to try some things out and offer any assistance if I can.
Cheers
GAM.
Hi GAM,
> Anyway, the issues I was experiencing are:
> 1. Parcel quoted when weight and dimensions < Large Letter
> maximums.
> 2. iirc, a single item <9cm x 9cm x 1.5cm returns 'at least one
> dimension is invalid' and also, iirc, > above but < max. letter
> returns '...max. girth exceeded...' or similar error msg.
> 3. Specifying the mentioned 50mm x 50mm x 30mm didn't
> work either.
> I looked at tricking the 'stack' method by specifying 0.5cm and
> 9x9cm so that it would accept Large Letter for 4x product of this
> size. It didn't work, iirc, max girth msg.
To fix this, load /includes/modules/shipping/austpost.php into a text editor.
Look for the line that reads:
if ($dest_country == "AU" ) {
Then immediately before this line add the following:
----------------------------------------------------------------------
$var = array($swidth, $slength, $sheight) ;
sort($var) ;
if ($var[0] < 50 { $var[0] = 50 ;}
if ($var[1] < 50 { $var[1] = 50 ;}
if ($var[2] < 50 { $var[2] = 50 ;}
-------------------------------------------------------
This should fix those errors.
> Also, if you can explain or point me in the right direction on how to > enable/disable debugging this would be a great help as I would like > to try some things out and offer any assistance if I can.
Somewhere around line 96 of the file mentioned above you should find a line that contains "debug = 0". Change this to "debug = 1".
Note: The output isn't particularly pretty and you may not find it'll give all the information you need. Give it a go though.
BTW, when it comes to letter rates, the austpost server doesn't get contacted at all. The rates for these are predefined in the config options. The Austpost server will only quote for parcels, which is why it produces errors when it gets fed data that is considered 'too small' to be a parcel.
Cheers
Rod
Hey Rod
The letter rates vs parcel rates makes total sense. I'll insert the changes you mention and have a look at the debugging a little later this afternoon or this evening (Wifey is cracking the household whip for the moment ;)).
I'll let you know how it goes.
Thanks heaps Rod!
Cheers
GAM
Hi David,
> Connection Failed
>The system returned:
> (110) Connection timed out The remote host or network may be >down. Please try the request again.
I'm currently getting the same error (10am Sunday 18th). All we can do is wait until they fix it.
As GAM said, the server doesn't go down all that often - its just a pain when it does, and unfortunately, when this occurs control is taken away from the AP module so it isn't easily possible to generate more friendly error messages or take other corrective action.
Cheers
Rod