Reference error onpage using Facetwp

Hoi Rob, @robruifrok,

There’s a dependency on a Google Maps script in the front-end.min.js of FacetWP. The only way to fix this is by blocking this script until Maps is loaded, the issue is it has more functionalities not related to maps, making it impossible to block without losing these functionalities.

The proposed fix is the WP Consent API, whereby plugin developers can conform to an API when these cases occur. You can ask FacetWP if they’re willing to conform, we can help them if needed.

The fastest way is to release Google Maps entirely, by disabling it under Complianz – Integrations.

This might not be the answer you were hoping for, but it’s an issue that can’t be cleared right away.

groeten Aert

Thank you for the very fast aswer.
Unfortunately disabling maps in the integrations screen does not solve the problem.

Hi @robruifrok,

Could you disable WP Optimize so I can have a better look at the files?

If there are any other plugin integrations or services that might relate to Google, try disabling them too, until we have the culprit.

First guess is the Google API is still blocked.

regards Aert

Hi Aert,

Other integrations using googlemaps are Avanced Custom Fields and Mapprerss maps for wordpress. Switching off ACF integration solves the problem.