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.