• Resolved agrolsy

    (@agrolsy)


    When Autoptimize is enabled only the ViewPage event is fired, ViewContent isn’t. Could you help me sort that out?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    Firstly, please check this topic in order to troubleshoot your issue: https://www.ads-software.com/support/topic/before-posting-to-read-before-posting-a-topic/

    If you were not able to fix yet, please post here the URL of your website so I can check. I checked Autoptimize on my end and the plugin works very well even with the plugin and its settings activated.

    Let me know.

    Thread Starter agrolsy

    (@agrolsy)

    I’m still having the same problem here: https://klickerforlaget.se/butik/med-passion-for-det-vilda/

    the viewcontent isn’t fired, see screen shot from pixel helper below
    with autooptimze enabled: https://snag.gy/OW8T1c.jpg
    without autooptimize enabled: https://snag.gy/UGCgTd.jpg
    error message: https://snag.gy/4lu3HS.jpg

    woocoomerce, 3.6.1
    wordpress, 5.1.1
    pixel caffeine: 2.0.7
    browser: chrome
    same thing happens with theme twenty nineteen (I use a Divi child theme on the site)

    Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    apologies for replying only now.

    I see the page you posted and the pixel is fired correctly. Anyway, accorgind to what I see in the “error message” screen, that error may cause the issue you are talking about, but it should be caused by some other plugin you have, because Pixel Caffeine doesn’t have any “Cookies” instance inside the Javascript code.

    Try to troubleshoot by deactivating all plugins and re-activating them one by one, checking for the issue meanwhile. Remember to clear the cache (if any) in Optimizely after each plugin activation/deactivation.

    Thread Starter agrolsy

    (@agrolsy)

    I deactivated the autoptimize and don’t use it any more so I haven’t looked into the problem more.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin conflict with Autoptimize’ is closed to new replies.