Carlos Minguell Posted Wednesday at 11:24 AM Posted Wednesday at 11:24 AM Hello, Yesterday, a customer of my store received the error "Your request has not been processed. Please contact the administrator. Your support ID is: (number)" when trying to complete his order. Since the checkout process was working correctly for the rest of the customers and after extensive testing, I discovered that the error occurs when the customer's name has an accent on the first letter (For example Óscar). I don't suppose it's something I can fix, even with the help of the forum, but I'm posting it here so you're aware of the bug. Thanks and best regards,
datakick Posted Wednesday at 12:34 PM Posted Wednesday at 12:34 PM I don't think it's a bug in the system. I have no problems creating customer accounts with that name, or creating orders. My guess is that your database charset / collation is not correct. Use core updater to check if your database tables use correct character set and collation. It should be CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
Carlos Minguell Posted Wednesday at 03:21 PM Author Posted Wednesday at 03:21 PM Many thanks for your reply, There are no problems creating customer accounts with accent in first letter of name, the error is showed when the customer clics on the "pay with credit card" button in the fifth steep. When the word with the accent is in the surname or other field, the problem doesn't appear. I have Applied fix in Database Schema to some lines that showed "..._unicode_ci" instead of "..._general_ci", but the error appears again. In Core Updater there are also a lot of lines with the error you can see inthe attached image. Should I fix it or is it not important? Many thanks and best regards,
datakick Posted Wednesday at 03:52 PM Posted Wednesday at 03:52 PM What payment module do you use for card payments?
Carlos Minguell Posted Wednesday at 04:15 PM Author Posted Wednesday at 04:15 PM The official module from REDSYS
datakick Posted Wednesday at 04:21 PM Posted Wednesday at 04:21 PM Check if you can complete order using other payment method. If you can, then it's a bug in this third party module. Ask developer to fix it, or hire someone
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now