Printable View
Not me.Quote:
Originally Posted by dw08gm
The modules serve different purposes, The package Tracker is designed for tracking packages (obviously), where as the ozpost module is designed to provide shipping/postage quotes.Quote:
Originally Posted by dw08gm
I've never installed the Ty Package Tracker so I can't say if it will work with ozpost or not, or more specifically, wherher it supposrts the same carriers that ozpost does.
Cheers
Rod
Hi Rod
Yes Ty Package Tracker comes with direct links to USA carriers for the download and display of tracking information via account, although I have yet to realise the extent of that information.
And these links would need to be changed for Australian carriers eg AusPost, Fastaway.
However whether the Australian carriers provide useful tracking info has yet to be seen by me from previous experience.
If OzPost provides links to the tracking facilities of certain services of the Australian carriers, that could automatically be included in an order confirmation email, this would be sufficient for my current needs without having to bother with Ty Package Tracker.
Cheers
Won't happen, unless ozpost.net expands to make bookings as well, because unless/until a booking is made there won't be any reference data to include in the emails... and I really can't see ozpost.net ever evolving into a booking service as well as a quotation service, primarily because Australia Post don't provide a standard booking/tracking service (Eparcel is not the same), and secondly, because most of the courier companies are very difficult to work with in regards to product integration.Quote:
Originally Posted by dw08gm
Cheers
Rod
Hi Rod
Thanks for the extra clarity.
As a bit of background to my initial query, provision for Ty Package Tracker is being incorporated into the new EditOrders 3.0 and SuperOrders 3.0 mods about to be released. However, these mods do not require the installation of Ty Package Tracker.
You need to contact the tnt helpdesk and ask that the RTT ('Rated Transit Times' service for your account be enabled.Quote:
Originally Posted by QCTechnologies
You DON'T need to change/alter your current username/password (these produce a different error message), you'll find it'll just start working as soon as it is activated.
--------------------------------
CIT Helpdesk
If you are experiencing difficulties accessing the TNT website or experiencing problems with TNT's online services please send us your enquiry. If you prefer to speak to a member of our CIT Helpdesk please call our Technical Support Team on 1300 851 131.
---------------------------------
Cheers
Rod
I have tried these postcodes 0820 0885 0822; not working with V2.2.0 V2.1.1
1.3.8a
ecolitecandles.com.au
paid 3 or 4 days ago; but http://www.ozpost.net/postage.php?fl...&fromcode=0885
V2.1.1:
Debugging information Item 1-1Large Faerie with Flower in her Hair ParcelWeight 6100gmsItems 1Weight 6710gmsDimensions 29 x 25 x 2.5 29 x 25 x 2.5 Cube / Weight 1812.5cc / 0.453125Kgs 1812.5cc / 0.453125Kgs
Submitted: Length=29.00cm, Width=25.00cm, Height=2.50cm, Weight=6710gms, NumBoxes=1Server response time 0.45msServer Returned:
Error0.00-1Invalid input Data [Suburb error] 74.55.148.130 Wed Dec 15, 2010 19:07 (SA Server Time) 18:07 (NT Store Time) 0.00 0.00 BAGOT N/A 60
##################################################
p.s.
V2.2.0 on 1.3.8a does not echo shipping module name; I am still using old ozpost update_product.php collect_info.php; and that still seems fine.
nothing is working at the moment (even for the free aust post); no post code are working for any module. but I see the remaining days is fixed. I dont know I will try again tonight.
I think it would help a LOT if you mention what the actual problem is, before explaining what you have tried in order to fix it. :-)Quote:
Originally Posted by vandiermen
Each storename/postcode creates a new database entry, each with a new 60 day trial period
This link curently shows 58 days until expiry.Quote:
Originally Posted by vandiermen
EcoLite Candles/4870 shows 1095 days until expiry.
This means at the time of registration I identified EcoLite Candles/4870 as being the actively used store rather than the specified EcoLite Candles/0885 ... (Actually, that would have been the only active one at the time, because if I'd identified multiple combos for the same store I would have updated both records, which I have now done).
In any case, this doesn't explain what the problem is, because with 60 days or 1000+ days subscription this aspect of things isn't going to make any difference.
I've reformatted the relevent part of your debug (above) to help make it a little easier to read:Quote:
Originally Posted by vandiermen
Firstly the error:
Invalid input Data [Suburb error]
This can be either the store origin suburb, or the destination suburb..
The "74.55.148.130" indicates the server IP address (prep work for multiple servers rather than simple redundant servers)
Wed Dec 15, 2010 19:07 (SA Server Time)
18:07 (NT Store Time)
These lines are pretty obvious :-)
The servertime is used for logging purposes, the Storetime is used to ensure next day delivery deadlines match the store timezone
BAGOT N/A
These are the origin suburb and destination suburb (ok, not exactly obviious until informed). In this case a destination suburb cannot be found (N/A), this can be caused be a lack of a destination postcode, or an invalid postcode.
EcoLite Candles/820 (BAGOT) was the store origin used with this particular test.
The final entry "60" is the subscription remaining days, in this case it was the same day you started using this particular storename/postcode combo.
SO, if the destination suburb is your problem you'll need to ensure that you are testing with valid destination postcodes. This has gotten a lot stricter over the last couple of versions due to inaccuracies with single postcodes covering multiple suburbs.
If you find valid postcodes that still don't seem to work please let me know which ones and I'll take another look.
As for the store/origin postcode, sooner or later you'll settle on one or another (most people don't get this choice), and sooner or later I'll match whatever is settled upon with the data from the records that were subscribed with.
Where is it that you are not seeing this? (a screenshot may be helpful.. or not.. ). LOLQuote:
Originally Posted by vandiermen
The update_product.php collect_info.php and other files under /admin never need updating between ozpost module versions. They *may* require updates with *zencart* versions though (but to be perfectly honest, I don't recall when I last updated them).Quote:
Originally Posted by vandiermen
Oh, and please remember that when switching between versions it is imperitive that you click the remove/install button sequence in order to keep the database syncronised with the files.
Cheers
Rod
I've absolutely no explanation for any of this.. I've been away from the computer until shortly before replying to your first posting.Quote:
Originally Posted by vandiermen
Cheers
Rod
problem seems to have been V2.1.1 tpl_modules_shipping_estimator.php is not compatable with V2.2.0 or aust post moduleQuote:
Originally Posted by RodG
its all fixed now.