404 error in backend console – file missing

Hello @doffine

This file should be present in our package, I checked it in our installation package and it is present in the location “wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/resources/js”. It seems something might have gone wrong during installation. You could install the plugin once more and see if this gets corrected. You might want to do this manually, by downloading this package and uploading and installing it manually on your site.

Please let us know if this resolved the issue.

Kind regards,
Joost

Hello @joostvandevijve,

the 404 shown in the console doesn’t come from “wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/resources/js”

It is “GET https://[DOMAIN.TLD]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/assets/js/gzd-compat.js?ver=1.9.5
[HTTP/2 404 Not Found 917ms]” – and in this location the file is missing in the package.

So you write “resources”, but the file obviously is searched in “assets”?

Greetings,
-doffine

Hello @doffine

No, this is not a resource, but the location of the js file that the error is referring to. Please try to re-install and see if the error persists.

Can you also confirm that you have updated the plugin to version 2.0.0?

Kind regards,
Joost

Hi @joostvandevijver,

we cannot update to version 2.0.0, because version 2.0.0 has some bugs that make it unusable for us as you can see in other entries here in the forum.

Again: The problem is that the installation searches for the file https://[DOMAIN.TLD]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/assets/js/gzd-compat.js?ver=1.9.5 that causes a 404, because the file is in another location in the package.

Greetings,
-doffine

Hi @doffine,

Thanks for the input!
The development team will look into this and resolve it for the next bug fix update.
The Germanized compatibility was extended in the 1.9.5 update, and so this message should not occur in previous versions. But we generally recommend staying on the latest version that works well for you.

Kind regards,
Niklas

Hi @doffine,

This error has been resolved for the upcoming update 2.0.1.
If you’d like to give it a try, a pre-release is available for testing from here, but the official release should follow in the coming days.

Kind regards,
Niklas

Hello @doffine

Yesterday we release the official version of 2.0.1 that should resolve this issue. Please give it a try and let us know if you are still encountering this problem. We will mark this thread as resolved.

Kind regards,
Joost