Plugin Conflict with PixelYourSite (Pro)

  • Resolved johannes89

    (@johannes89)


    6 years, 1 month ago

    Fist of all the plugin is fantastic it really does what it should and helped me reduce the number of calls on my staging site from ~130 average to 54 which a huge page speed advantage.

    The only downsite right now is that my tracking does not work anymore, thats why I had to disable it again. I tried to contact the auther of the plugin via his website but no answer yet so I hope somebody here can help me with that.

    I am running on siteground with SG Optimizer and I was using the Asset Clean Up. For consent management I use cookiebot, but I tried differnt one so it seems not to work no matter what consent I use.

    If I enable the Asset Clean up, even after the consent there is no pixel or anything firing. I contact the plugin authors of PixelYourSite as well and they told me it is probably a Javascript that is somehow blocked but they cannot help me because the plugin “Asset Clean Up” is quite complex.

    So I hope anybody here can help me with this topic 🙂

    Thanks and best regards
    Johannes

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    6 years, 1 month ago

    @johannes89 first, my sincere apologies for replying so late!

    Fist of all the plugin is fantastic it really does what it should and helped me reduce the number of calls on my staging site from ~130 average to 54 which a huge page speed advantage.

    I’m very glad to hear that and the plugin will be improved in time just like it used to be so far!

    If I enable the Asset Clean up, even after the consent there is no pixel or anything firing. I contact the plugin authors of PixelYourSite as well and they told me it is probably a Javascript that is somehow blocked but they cannot help me because the plugin “Asset Clean Up” is quite complex.

    After checking your website, it makes sense that you could be having issues with PixelYourSite. It loads the following scripts that are having the “defer” attribute:

    • /wp-content/plugins/pixelyoursite-pro/dist/scripts/jquery.bind-first-0.2.3.min.js
    • /wp-content/plugins/pixelyoursite-pro/dist/scripts/vimeo.min.js

    The problem is that you’ve applied “Basic” preloading to these two scripts that aren’t meant to be preloaded. I’ve seen this behavior several times with users having similar issues. In fact, this situation made me think that it is necessary to add an alert message when the preload feature is used and there’s already an “async” and “defer” attribute added to avoid situations like this one.

    So, please remove the preloading, clear the caching, and re-test it. Out of curiosity: is there a reason you decided to preload these two scripts or you just thought it’s a good idea to have them loaded among the first (even though it’s not a good idea in the end)? Any answer would be helpful. Perhaps the preloading feature is not explained well enough and I need to explain it better.

    Thread Starter johannes89

    (@johannes89)

    6 years, 1 month ago

    I actually have no idea about the defere etc. so i might activated this by accident. Are there any other conflicts on the side with settings from your plugin or can we setup a review of those – I saw you are offering consultings as well 🙂

    anyany

    (@anyany)

    6 years ago

    @johannes89 or @gabelivan – where in the plugin do you apply/remove “Basic” preloading for these scripts? I have the same problem (when Asset Cleanup is activated, there is no pixel) and I don’t know where to change these settings that you mention in the plugin. 😛

    Thank you for your help!

    Plugin Author Gabe Livan

    (@gabelivan)

    6 years ago

    @anyany recently, there was an issue reported with Pixel Your Site (Pro) and Asset CleanUp related to the fact that /wp-content/plugins/pixelyoursite-pro/dist/scripts/public.js wasn’t loaded. That was because one of its “parent” file (which is the well known “js-cookie” handle) that was required to trigger first was unloaded. So, if you unloaded “js-cookie” (the path is usually /wp-content/woocommerce//assets/js/js-cookie/js.cookie.min.js), please make sure it’s loaded back.

    If that’s not the problem and you have preloaded by mistake (or whoever worked on your website, perhaps your developer) the JS files from “Pixel Your Site (Pro)”, just edit the drop-down from “Preload (if kept loaded)?” to “No (default)” and after you save the changes, it shouldn’t preload those JS files anymore. I hope it helps!

    @johannes89 My sincere apologies for not getting back to you sooner about your question related to any other conflicts. Besides the just mentioned one with “js-cookie” (which is not a conflict, but a user mistake which can be avoided) and the preloaded JS files (which it’s better to leave them not preloaded), I don’t know of any other conflicts with “Pixel Your Site (Pro)”. It’s been working fine so far for anyone using both plugins. As for consulting, yes, I can offer them via Zoom/Skype. If you’re interested, you can let me know on private via https://gabelivan.com/contact/ and we can take it from there. I can give you a discount as an apology for not getting back to you sooner as I’m usually proud of Asset CleanUp’s customer support 🙂

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Plugin Conflict with PixelYourSite (Pro)’ is closed to new replies.