reading i18n

Hi @alovalwp,

Thank you for reaching out. I completely understand your concern about encountering an error while browsing a product. Be rest assured that we’re here to help.

To assist you better, I’d like to clarify where exactly you’re seeing this error. Is it appearing on the front end of your website (what visitors see) or within your WordPress admin area?

Please share a screenshot of the error so I can get a clearer picture of what you’re referring to. You can use this tool to upload your screenshot: https://snipboard.io/.

Hi @alovalwp,

Thank you for the screenshot! I can confirm the error message is showing in your browser’s developer console and originates from the main.js file of the WooCommerce Google Analytics Integration plugin.

The message Cannot read properties of undefined (reading ‘i18n’) typically means the script is trying to use a translation or localization variable that hasn’t been properly initialized. This might not break your site visually, but it could interfere with some tracking functions or cause other scripts to behave unexpectedly.

To better assist, could you let us know:

• Are you seeing any visible issues on the site itself (like tracking not firing, unexpected behavior, or missing elements)?
• Did this start happening after a recent update to WooCommerce, the Google Analytics plugin, or your theme?

You can also try running a quick conflict test:

• Temporarily switch to a default theme like Twenty Twenty-Five
• Deactivate all plugins except WooCommerce and the Google Analytics Integration plugin
• Then check again for the console error on the product page

After running the conflict test, please share your System Status Report with us so we can take a closer look at your environment. You can find this under WooCommerce > Status > Get system report > Copy for support and paste the contents into https://pastebin.com or https://quickforget.com, then share the link here.

Once we have more details, we’ll be happy to help you troubleshoot further!

Hi there!

Thanks for running the conflict test! Since the issue didn’t occur with all other plugins deactivated, it’s likely being caused by a conflict with one of the other plugins on your site.

To narrow it down further, I recommend reactivating the other plugins one by one while testing after each activation. This should help you identify which specific plugin is causing the conflict.

Once you have identified the conflicting plugin, keep it deactivated or alternatively contact the plugin’s support team and ask them to help you fix the issue.

Let me know how it goes.