-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid API key error message #287
Comments
Forgot to add this is on a clean install of Prestashop, so no upgrade of a MyParcelBE module on an already functioning PS |
This shouldn't happen of course, but it's only a visual problem, if you refresh the page it should show as being saved correctly. Could you send us the logs you can download from the debug options in the settings, to [email protected]? |
Hi, I have the same problem. |
There was an issue with the migrations in We've just released a bugfix in If it doesn't immediately fix the problem, you could additionally try to clear any prestashop caches and/or uninstall and then install the latest module release. |
Hi, The error still exist. The installation from module myparcelnl has failed. Error: SQLSTATE[23000]: Stack trace: |
MyParcelNL version
MyParcelBE v4.2.0
PrestaShop version
8.20
PHP version
8.1.30
What went wrong?
Upon install of the module proceed to configure and fill in the API key found in your MyParcel backoffice. & click save.
Error displayed:
"Invalid API key
Please check if you have entered the correct API key."
Exit the module configuration and do something else within Prestashop back office and go back to the module configuration.
You now get to see the message "Connected to MyParcel" and the rest of the setup options/screens.
Now click Edit API ley and press enter in the API key field (the key was copied from backoffice so it should be correct anyway), result: Invalid API key error AND still/also the "Connected to MyParcel".
Now click Debugging and next Manual Update, result: Invalid API key error AND still/also the "Connected to MyParcel".
Reproduction steps
See steps described above
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: