When attempting to associate your PrestaShop Account with your shop, you may encounter certain error messages, often written in English. Here are the errors concerned and how to resolve them.
"Your shop is already linked and verified. You are not the owner, you can't unlink this shop"
Why this error message?
This error occurs during an association attempt, if an old email address was already associated but the dissociation did not work properly.
What solutions?
For security reasons, first, it is advisable to ask the user who made the association to dissociate it. If this is not possible but their account is still accessible in the back office, change the password and dissociate it.
If you do not have access to the account or contact with the person who made the association, contact us and we will be able to help you.
⚠️Always keep a record of the credentials that allow access to certain modules, even if you work with an agency or a freelancer. |
"The shop has not been verified. Reason: Error while sending tokens"
Why this error message?
This error occurs when the exchanges between the PS Account module and your store are blocked.
What solutions?
Check if the PrestaShop Account module is up to date. If so, update the module and try to reconnect.
If the module was indeed up to date, the problem you are experiencing may be due to the fact that your domain uses Cloudflare, and it is blocking the URL of the PS Accounts request. In the Cloudflare activity log, you will find an action with the status "Block" when you try to associate your shop. Authorize this request and try the connection again.
Finally, check with the help of your host that its settings do not block the call to your shop (Firewall, proxy, etc.).
"<psaccounts>integration: Given context is invalid: "currentShop.url" must be a valid uri"</psaccounts>
Why this error message?
This error occurs when the name given to your back office contains spaces.
What are the solutions?
Modify the name of the back office directly from the FTP by removing the spaces. Then check that access to the module is once again available.
Comments
0 comments
Please sign in to leave a comment.