Jeff Williams

We have the same issue & after a few emails back & forth we got a shrug from NitroPack, saying they can’t help us.

Maybe – I was just reading on another site that this sort of issue could be caused by incorrect character encoding in the DB & they recommended setting the DB to utf8_general_ci … I checked & we’re using utf8mb4_unicode_ci. I will readily admit that I don’t understand the difference between the two, it seems to me that UTF8 is UTF8

This seems to suggest that our setting is correct, though: https://stackoverflow.com/questions/766809/whats-the-difference-between-utf8-general-ci-and-utf8-unicode-ci

• This reply was modified 5 years, 11 months ago by Jeff Williams.

I did, actually, so even with the slight snark this is a bit helpful.

The thing is that these instances aren’t originating from anywhere in particular such as Russia, Ukraine, the Middle East, etc. & quite a few are American in origin.

I don’t think that this is something that itsec is doing, no, and it’s entirely likely that there’s a misconfiguration somewhere on our install, god knows that this one has been heavily modified.

Since it’s a malformed URL, I took a look in PMA & there are over 5300 instances in itsec logs since the end of October (we’ve been insanely busy so I didn’t pick up on this previously) & 64 in WF logs (yes, we run both) but I don’t think WF stores data as long as iThemes does.

@roweenaweb

Thanks for that, worked a charm on the site I was troubleshooting. Not sure why we didn’t include Woo support initially, we normally do.

Mike, to beat the dead horse a bit on the order info, we integrated Pushover for our team this year, which was a godsend. Unfortunately, now we’re seeing blank data in there because of it. Our order notifications on Pushover are hit or miss now, much worse than previously, & there’s never any information on what was ordered, just the amount. Is this something that would be fixed if the “enhancement” that we’re voting on in the ideas to improve/restore woo functionality is implemented?

Resolved

Mike, you are a gentleman and a scholar – THANK YOU!

No joy, Mike, same error occurs.

Hey Mike!

The only place we’d be able to look would be via the plugin editor for the AfterPay source code – their docs are here but I’ve not found what we need there.

The other gateways, Stripe & PayPal Standard, work as intended.

Thanks for the reply Mike, I take it the additional info is a non-starter at this point. I’m not sure that I have anything to add to the Git for duplicate emails other than “me too” & that’s probably not that helpful.

Cheers, Alin! I’ll add it to my to-do list.

Alin, we’ve had this exact issue on several client sites & while I grant that it’s a simple fix to reauthorize, most of the clients don’t understand this & end up coming to us to resolve the issue.

My question is why is it happening in the first place & what can be done to resolve the issue?

We really like how you’ve set the plugin up but the irritation factor with dozens of sites having this issue is mounting & this is becoming kind of a time suck for us. If we need to do something, please let me know.

• This reply was modified 7 years, 9 months ago by Jeff Williams.

Following

Hey Matt,

I’m not sure what this may be aside from FM and not the good kind. There’s really no reason for it not to be working but it isn’t. Since this is a client’s production sir, I need to make them whole as soon as I can, so I opted for a different solution for their site.

I definitely appreciate the attention to this issue but for sanity’s sake, I’m marking this as resolved.