My apologies. I realized it wasn't appropriate about 10 minutes after I posted it and that's why it got deleted by me right away. I hate to see software publishers struggle when they don't need to, but you're all correct, I shouldn't post that way on this type of message.
- Dan --- In [email protected], Simon <macdevelo...@...> wrote: > > As most Kagi suppliers will know, they have now been moved over to a > new data reporting format (which they have been phasing in over last > the few months). I have noticed that an old problem still exists > (among many). > > If a customer purchases your product multiple times, your ACG (code > generation script) gets called multiple times. Unfortunately Kagi > stuff all the results into one tiny field rather than breaking out > multiple rows. So the registrationName field now has "Joe Public > Joe Public Joe Public" and the registrationCode has "1234-ABCD > 5678-EFGH 9012-IJKL". You get the idea. Rather than analysing the > reports, I have to look at regular expressions. In fact, they also > manage to mangle up the TFYP emails in such multiple orders, with > customers quite confused. > > Interested to know how many Kagi suppliers have experienced this and > have also raised this issue over the years. I have. Yet still > nothing gets fixed. Not to mention they still mangle the > registrationName, so if you're in Japan, your name could end up being > **** because foreign character sets aren't handled properly. > > This is not to knock Kagi, as every payment processor has their > problems, but I think suppliers have been quite patient. If a group > of us got together and highlighted the main improvements we would like > Kagi to focus on, do you think they would listen? > > --Simon >
