@metuza nice job on the investigation – one of the big sites we handle has been dealing with this problem. It caused a ton of issues. We added a front end hack to send this to lowercase, without deeply understanding this issue. Your explanation helps us realize this wasn’t a conflicting plugins, misconfiguration, or anything besides a mistake on the end of WooCommerce.
Thanks @lovingbro for addressing it quickly on your end. This stuff happens, and it’s important it’s handled well, which I think you guys did.
@manuelski thanks – I had to guess the URL to find it. I didn’t know about the advanced view before.
I’m debating about trying to patch this…. It’s going to be super annoying remembering to skip this update. I could probably change the plugin name, so the update mechanism breaks.
