Mmm. Rod, firstly I want to make in crystal clear that I very much appreciate your work. I too have been using the AusPost module on a commercial client's site, and without it ZC simply would not have been an option.

But to hear that it is no longer working correctly (by accident really) was pretty concerning. I understand ZC is OS, and what that effectively means to my clients is cheap. Heck, if they could/would pay of course I would use a commercial product. But up until now I always believed that ZC *could* work with the right support and technical knowledge.

But this scenario with redundant modules is extremely troubling. The AusPost - improved module is still available, listed as compliant with v1.3.8 AND seems to install & work fine with v1.3.8a - I know because I have it installed on a pre-production site.

As having *some* experience in ecommerce IMHO anything to do with money needs to be pretty set-in-stone, so I see it as a *huge* flaw in the whole ZC logic to have redundant modules involved with financial calculations available that *look* to be compliant with the latest release. Imagine if one of the credit-card modules were to be totally compromised, surely the ZC team would *have* to remove it.

I hope that the Zen Cart team do indeed take this on-board. Sure, there are suggestive reasons why old code may still available to download (though overall I disagree), but surely there should be the capacity for the "owner" of the module to indicate to potential users that there are serious flaws with the code and inform the general public that is no longer being supported.

Suggestion 1.

I think an easy solution might be for the Zen Cart forum to have threads that are specific to each module and *only* contain information from the writers/owners/updaters of the code. Means that critical information is easy to find and gives end-users a clear date-stamped picture of the status of this module.

Suggestion 2.

I think that you should consider charging an "optional" support fee for your code. Not sure if you can do this according to the ZC *laws*, but as this module is pretty mission-critical for my installs (I'm based in Unley, not far from you of course) I not only need it to work but need to know what issues are happening with it. So by being "registered" with you means that you would "most likely" email me with updates on the status of the module.

The new version of my clients site uses a third-party commercial credit card payment system (upgraded from the Ceon module) for two reasons:

1. PCI-DSS compliance
2. Keeping this part working is their problem, not mine.

FWIW I would be more than happy to pay an annual fee for you to keep my contact email on your mail-out list. Food for thought.

-------------------------------------

On a more technical side, can you give me any more detail as to why a server-change (yours or theirs?) is preventing the AusPost module from working properly? The obvious reason I ask this is does the new OzPost module potentially suffer from the same issue?

Cheers, Adrian