• Resolved shahank

    (@shahank)


    Noticed a new console error on the latest plugin update. I see this error on both my websites [ redundant link removed ]. This is the error Uncaught ReferenceError: adsTringId is not defined. Don’t know if it’s something I don’t need to worry about. Thanks again.

    • This topic was modified 3 years, 8 months ago by Jan Dembowski.

    The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Conversios

    (@tatvic)

    Hey @shahank ,

    We are working on this issue and we will release an update soon for this.

    However, this will not break any functionality you are using.

    Plugin Author Conversios

    (@tatvic)

    Hi @shahank,

    We have had a look at both the stores [ redundant link removed ] and observed that the older plugin version(2.3.6) is still active.

    Here, we would suggest activating the latest plugin version(3.0.1) so that we can have a look at the issue faced. Also, please share the plugin setting screenshots for the latest version.

    Thread Starter shahank

    (@shahank)

    I don’t have 2.3.6 active, I have 3.0.1 active. Didn’t have this error with version 2.3.6. I have attached two 2 screenshots Image 1 and Image 2 showing the settings page.

    • This reply was modified 3 years, 8 months ago by shahank.
    • This reply was modified 3 years, 8 months ago by shahank.
    Thread Starter shahank

    (@shahank)

    Issue still present with update 3.0.2.

    Plugin Author Conversios

    (@tatvic)

    Hi guys,

    We tried to identify the root cause of the error and concluded that it is not occurring due to the plugin rather it is happening due to the inline JS minify enabled on the store pages.

    To give you more context: The inline JS minify does not let the plugin get the required value in the adsTringId variable and which is why the error occurs.

    Just to mention, the error will not break data trackings in Google Analytics, GA4, etc.

    Currently, we are identifying possible & effective solutions to manage the error via our plugin.

    Workaround: You can get rid of the error by disabling the inline JS minification on the store pages.

    Hope the workaround helps.

    Thanks & Regards,
    Tatvic Analytics.

    Same here even disabling the inline js minification.

    • This reply was modified 3 years, 8 months ago by nhm_pt.

    Litespeed server
    Version 3.0.2
    no minification

    ruins my js

    View post on imgur.com

    View post on imgur.com

    I’m not great at JS but I think check like
    typeof adsTringId != “undefined” / in front of current one could do the trick

    Same here:

    Litespeed server
    Version 3.0.4
    no minification also

    Uncaught ReferenceError: adsTringId is not defined
    at t_products_impre_clicks ((index):1524)
    at HTMLDocument.<anonymous> ((index):1623)
    at i (jquery.js?ver=1.12.4-wp:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
    at Function.ready (jquery.js?ver=1.12.4-wp:2)
    at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)

    • This reply was modified 3 years, 8 months ago by nhm_pt.

    Same error.
    Using autoptimize plugin for minification, but inline js minification is turned off. Somehow the part of code that outputs adsTringId never makes it into html.
    Current workaround is to use older version, 2.6.3.1

    I would recommend reworking that inline js with a standard js file and sending variables with wp_localize_script.

    • This reply was modified 3 years, 7 months ago by MSTannu.

    Also seeing this issue still in v 4.1.1

    Issue still present. Any update on this?

    Issue is still present in version 4.1.3, both with and without autoptimize active. Example page: https://www.romerskincare.com/product/cleanse/

    jquery.min.js?ver=3.6.0:2 Uncaught ReferenceError: adsTringId is not defined
    at t_products_impre_clicks (<anonymous>:65:40)
    at HTMLDocument.<anonymous> (<anonymous>:144:21)
    at e (jquery.min.js?ver=3.6.0:2)
    at t (jquery.min.js?ver=3.6.0:2)

    Please tell me how to get rid of this error, every page has this error, which causes each page to take longer to load, which seriously affects the website’s Google ranking.

    I’m closing this old thread here. @kaiyang and oters, if you need support, please start your own topics instead. The form for that is located at the bottom of https://www.ads-software.com/support/plugin/enhanced-e-commerce-for-woocommerce-store/

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Noticed a new console error on the latest plugin update’ is closed to new replies.