search

myparcelnl / prestashop

PrestaShop module to integrate with MyParcel NL and BE
https://developer.myparcel.nl/nl/documentatie/11.prestashop.html
10 stars 5 forks source link

Invalid API key error message #287

Open kennethbruyninckx opened 1 week ago

kennethbruyninckx commented 1 week ago

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

kennethbruyninckx commented 1 week ago

Forgot to add this is on a clean install of Prestashop, so no upgrade of a MyParcelBE module on an already functioning PS

EdieLemoine commented 6 days ago

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 support@myparcel.nl?

mjonkers1989 commented 6 days ago

Hi,

I have the same problem. But is not only a visible problem. I have already send all the details to support@myparcel.nl But the same problem is also for myparcelNL.

FreekVR commented 12 hours ago

There was an issue with the migrations in 4.2.0 which appears to be causing breaks in Prestashop since they released 8.2.0. These errors were incorrectly being shown as validation errors for the API key on the module settings page.

We've just released a bugfix in 4.2.1, can you let us know if upgrading to this version fixes the problem?

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.