Bug After update to version 5 : ps_account "Error retrieving context"

[corrigerunbug]

Prestashop : 8.2.0
Prestashop Checkout : v8.5.0.5
Ps Account : v8.0.3 (verified) CloudShopId : ok

Error : Error retrieving context. Please try to reset or reinstall the module.
Problem persists after reset or reinstall the module

CORS error !

[matks]

Hello @corrigerunbug nice alias 😄

You are the 2nd person reporting this issue today. The first person investigated it and found it was Cloudflare blocking ps_accounts webhooks. I don't know if this can help?

Could you click on the Arrow on the left so we can see the full error message in the console?

Also could you please open a Support Ticket https://help-center.prestashop.com/contact?psx=ps_checkout

Having a support ticket will help us pinpoint your shop, identity, usage, and help us investigate

[corrigerunbug]

Hello, @matks

I have this Error even Cloudflare was disabled, im still investigagting that issue, i will give the solution after finding the issue.
I want to informe you that i have
also this :

• modules/ps_accounts/controllers/front/apiV2ShopProof.php
• modules/ps_accounts/controllers/front/apiV2ShopHealthCheck.php
  Give same error : Fatal error: Uncaught Error: Class "PrestaShop\Module\PsAccounts\Http\Controller\AbstractV2ShopRestController" not found in

[matks]

Very strange, because the code is here https://github.com/PrestaShopCorp/ps_accounts/blob/main/controllers/front/apiV2ShopHealthCheck.php

And the class not found is here https://github.com/PrestaShopCorp/ps_accounts/blob/main/src/Http/Controller/AbstractV2ShopRestController.php#L26

I also download latest ps_accounts zip https://github.com/PrestaShopCorp/ps_accounts/releases/tag/v8.0.3 and I find the files

[hschoenenberger]

In that specific case it really looks like the controller has not been installed properly most likely a failed upgrade or an upgrade that didn't run (module vendor triggered too early...).

[corrigerunbug]

CORS

Solution if no Cloudflare :
.htaccess backoffice

# Allow your backend origin 
# * replace with blocked assets 
Header always set Access-Control-Allow-Origin "*"
Header always set Vary "Origin"

# Methods and headers you use
Header always set Access-Control-Allow-Methods "GET,POST,OPTIONS"
Header always set Access-Control-Allow-Headers "x-prestashop-authorization, Content-Type, Authorization"
Header always set Access-Control-Max-Age "86400"

[matks]

Thanks for sharing, so this fixed the problem for you?

[antoinemetifeu]

CORS

Solution if no Cloudflare : .htaccess backoffice

# Allow your backend origin 
# * replace with blocked assets 
Header always set Access-Control-Allow-Origin "*"
Header always set Vary "Origin"

# Methods and headers you use
Header always set Access-Control-Allow-Methods "GET,POST,OPTIONS"
Header always set Access-Control-Allow-Headers "x-prestashop-authorization, Content-Type, Authorization"
Header always set Access-Control-Max-Age "86400"

Hello! Could we have the CORS errors, please?

[corrigerunbug]

Access to fetch at 'https://domain.ltd/adminfolder/index.php?controller=AdminAjaxV2PsAccounts&ajax=1&action=getContext&source=ps_accounts&refresh=true' from origin 'https://assets.prestashop3.com' has been blocked by CORS policy: Request header field x-prestashop-authorization is not allowed by Access-Control-Allow-Headers in preflight response.

[corrigerunbug]

Thanks for sharing, so this fixed the problem for you?

It fix the login to ps_accounts but Ps_checkout still not showing after connecting paypal account.

[corrigerunbug]

Now here is the new message :
The configuration is not set
You have an issue with your configuration, try onboarding again or contact our support

[matks]

@corrigerunbug I think you should contact support team https://help-center.prestashop.com/contact?psx=ps_checkout

It looks like the PayPal account you try to use has an issue. There could be plenty reasons behind that, they will be able to provide you the right one

[corrigerunbug]

@matks : The PayPal account functions properly with the [PayPal Officiel] module. I have already reached out to their support, but no resolution has been provided to date.

[matks]

Hello @corrigerunbug for your information we delivered PS Checkout 5.0.6 https://github.com/PrestaShopCorp/ps_checkout/releases/tag/v5.0.6 which contains 8 bugfixes, your issue might be one of them

[corrigerunbug]

Hello, @matks

Not working even after upgrade
I have fix it by typing manually this config

table : ps_configuration

• PS_CHECKOUT_PAYPAL_ID_MERCHANT : ID OF PAYPAL
• PS_CHECKOUT_PAYPAL_EMAIL_MERCHANT : MAIL OF PAYPAL
• PS_CHECKOUT_PAYPAL_EMAIL_STATUS : 1
• PS_CHECKOUT_PAYPAL_PAYMENT_STATUS : SUBSCRIBED
• PS_CHECKOUT_CARD_PAYMENT_STATUS : 1

after changing this it works fine

[ilbonte]

Hi @matks I am also experiencing the same error reported in this thread and haven't been able to solve it yet.

My context:
I am taking over a shop previously managed by an agency.
Originally, I had ps_accounts v7 installed. ps_checkout was also already installed (but not fully configured), and its Step 1 was linked to the old agency's account.

What I did:

1. I updated ps_accounts to v8.
2. I logged out of the old agency account in ps_accounts and logged in with my new owner account.
3. Since then, ps_checkout displays the "Error retrieving context" message.

Troubleshooting steps taken:

• I have tried uninstalling and reinstalling ps_accounts, ps_checkout, and ps_eventbus multiple times to clear any cached data, but it didn't help.
• I tried adding .htaccess rules to fix potential CORS issues, but that didn't work.
• I then used the "Allow CORS: Access-Control-Allow-Origin" browser extension. This successfully unblocked the requests: I no longer see any errors in the JavaScript Console or the Network tab (the requests return 200 OK).

Current status:
Despite the console and network tab being clean (no CORS errors visible anymore thanks to the extension), the "Error retrieving context" red banner still persists in the module UI.
However, if I check the ps_accounts module itself, it confirms that my shop is verified and linked to my new email correctly.

My questions:
Do you think I can proceed with the ps_checkout configuration (PayPal onboarding) despite this error banner? Is it safe to ignore it if the account seems verified in ps_accounts, or will this cause issues with payments later on?

Any advice on how to fully clear this state would be appreciated.

Thanks!

[ilbonte]

I digged deeper and found the issue of my problem:
the API call "https://mywebsite.com/myurl/index.php?controller=AdminAjaxV2PsAccounts&ajax=1&action=getContext&source=ps_accounts&refresh=true"
triggered by "psaccountsVue.js" was initially failing for the CORS error and after the "fix" with the extension it was returning a 200 BUT the content was not the expected JSON but instead an HTML returned bt the "firewall" of my host provider!

I'm not trying to contact the provider to whitelist this type of calls

[matks]

Hello @ilbonte I'm sorry I did not receive a notification for this thread :/ but I'm happy to see you found the solution

[matks]

Closing the thread since there was no activity for 2 months

[corrigerunbug]

the issue its still there @matks