lousaint

Great! Thank you for the quick response.

I seem to be having the same problem. However, we don’t set a SKU on the parent product, so it comes through with the product id.

Hello,

The renewal does seem to be suceedeing now. However, I’m still seeing two order notes on the order with two different transaction IDs: “SecureSubmit payment completed (Transaction ID: 1260082912)” and “SecureSubmit payment completed (Transaction ID: 1260075076)”, posted one second apart.

So far, only one transaction has shown up as pending on the card used for testing. It hasn’t posted yet, but an earlier test also shows only one transaction posted–so maybe it’s actually working correctly. The duplicate notes seem strange though. Is this normal? If not, any idea what’s going on?

Thanks.

I’ve discovered that we are still getting this error. However, I suspect now that the problem is not that bad zip codes are being somehow generated for new subscribers, but that these are actually existing subscribers who already had bad data in the zip code field–likely imported at some point from a csv file that had leading zeros trimmed by Excel. (The signup is for notification for a special event, so existing subscribers are likely to enter their email addresses to be notified.) I was just thrown off because the form seems to be updating the “Date Added” field.

When the form updates their profile, MailChimp is validating the existing zip code data throwing the error.

So, the source of the bad data and error is almost certainly not your plugin, but I’m still looking to keep this error from showing up. Perhaps cleaning up the subscriber data is the only way to do so.

I don’t have a good way of testing it, but I haven’t gotten further complaints, so I think this did resolve it.

Hi Kevin,

We don’t have any other forms that include the address or zip code field, but the zip code field is indeed set as required in MailChimp.