Wooptpm is not defined

  • Resolved bedbazaar

    (@bedbazaar)


    3 years, 1 month ago

    As visitor cookie consent is igrored, i added this code to load wooptpm before the inline scripts:

    add_filter( 'sgo_javascript_combine_exclude', 'js_combine_exclude' );
function js_combine_exclude( $exclude_list ) {
	$exclude_list[] = 'wooptpm_front_end_scripts';
	$exclude_list[] = 'ajax_wooptpm_get_cart_items';
	$exclude_list[] = 'ajax_wooptpm_get_product_ids';
	$exclude_list[] = 'ajax_purchase_pixels_fired_handler';
	$exclude_list[] = 'wooptpm';
	$exclude_list[] = 'wooptpmGoogleInlineScripts.js';
return $exclude_list;
}

    Constantly for 2 weeks the warning in console is gone but 50% sales are dropped.
    Because of loading wooptpm before other scripts my website’s loading speed is dropped from 60 to 40 on google pagespeed insights.
    Maybe the methode which i am using is wrong. Please can somebody guide me to solve this.
    Thankyou.
    Regards,

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author alekv

    (@alekv)

    Hi @bedbazaar

    The plugin already uses this filter to remove it from the SiteGround optimizer. So the method is correct, but should not be necessary. I’m still curious on why you think adding them yourself helped. Maybe there is something particular to your install that I haven’t covered in my plugin yet. Could you send the debug information from the support page to [email protected] ?

    The wooptpm.min.js file and inline scripts are relatively small and can’t cause such a drastic slowdown. Maybe Google Pagespeed Insights is inaccurate, or other factors are causing this.

    Regards
    Aleksandar

    Kenneth

    (@kavillarosa)

    Support conversation was resolved over [email protected]

    Thread Starter bedbazaar

    (@bedbazaar)

    Hello,
    Each update of plugin was awaited with the glimmer of hope to solve this issue. But it remains unsolved. My product pages are showing this issue yet https://prnt.sc/yCyW_8pM3aLN.
    Please can you guide me to solve this. Thanks.
    Regards,
    Rana

    Thread Starter bedbazaar

    (@bedbazaar)

    Dear this plugin is not fully tracking my website. I visited many woocommerce websites using your plugin but the same issues are not thr. But why you guys treating me apart? I just trusted on you and uploaded your plugin. But thr r different bugs created by this plugin as users are missing from the data segments and audience source is badly effected.
    Please reply me.

    Plugin Author alekv

    (@alekv)

    Hi @bedbazaar

    The issue you posted yesterday points to a problem that was solved in the most recent version. At the moment I see that the most recent version is installed on your server. When did you update to that version?

    Also, I visited the page in your screenshot and can’t replicate that error. Do you know how to “provoke” that warning message in the console?

    And I browsed several other pages on your website. Again, no error or warning appeared.

    To me it looks like the plugin works, at least mostly, fine.

    If you believe there are still problems I need to be able to replicate the bug in order to be able to analyse and fix it.

    Regards
    Aleksandar

    Thread Starter bedbazaar

    (@bedbazaar)

    Hello,
    Plugin is conflicting with Facebook for woocommerce plugin. I contacted with facebook support, they advised me to report this this issue to you. I have these issues on each product page when i activate woocommerce pixel tracking:
    https://prnt.sc/MDVhIDSz-m8i (in Safari browser)
    https://prnt.sc/mHa9C8qCpeoJ (in chrome browser)

    Regards,
    Rana

    Plugin Author alekv

    (@alekv)

    Hi @bedbazaar

    I still can’t provoke the same console error, neither in Chrome (https://monosnap.com/file/UOgPbBZZWDHjC1Dg6oEesZGen0RGvJ) nor in Safari (https://monosnap.com/file/f9yr6kGTP1fJI0CCRcqJ4HdNPlFkH5). Why I can’t replicate the same error is a mystery to me. I believe that it happens on your browser, just not in mine.

    On the bright side, I do have an hunch why the error is showing up. I will add a safeguard to prevent this in the upcoming version. But it may take a week or so since I am refactoring larger parts of the code and need to test it thoroughly before releasing it publicly. If you want to participate in a beta which includes the safeguard let me know at [email protected]

    Regards
    Aleksandar

    PS: In the meantime you could try out the Facebook integration of our plug in. It works well for many.

    • This reply was modified 3 years ago by alekv.
    • This reply was modified 3 years ago by alekv.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Wooptpm is not defined’ is closed to new replies.