-
Notifications
You must be signed in to change notification settings - Fork 2
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
You have requested a non-existent service "multisafepay.payment_option_service". #8
Comments
I get this message when I try to uninstall the module: Kan actie Uninstall niet toepassen op multisafepayofficial. You have requested a non-existent service "multisafepay.payment_option_service". |
Hi @mark-app.
Try to clean the cache by running the following commands.
Or maybe manually removing the content of the following directories:
Could you try these actions, preferably in a staging environment if you can reproduce the same issue there, and let us know if that solves the issue? == Alternatively, please, share with us:
And we will try to reproduce the same issue using same variables. |
@danielcivit I have already tried clearing the cache but unfortunately that does not fix the problem. I tested it with a live webshop on PrestaShop 8.0.1 with PHP 7.4.33. But also with a local test webshop on MAMP with PrestaShop 8.2 and different versions of PHP (7.4, 8.0.2, 8.1.31) |
Hi @mark-app Unfortunately, we have not been able to reproduce this issue, even using those versions.
|
I have the same issue with the 15.16.0 module You have requested a non-existent service "multisafepay.payment_option_service". Ps I’ve already cleared the cache |
|
Hi @mark-app It seems we didn't receive any more comments from your side. Is the issue fixed on your side? If that's the case, could you provide feedback about what happened? |
When I try to configure the latest version of the module in PrestaShop 8, I get the following message:
You have requested a non-existent service “multisafepay.payment_option_service”.
I cannot re-install the module either.
The text was updated successfully, but these errors were encountered: