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

    (@ti2m)

    Thanks for the feedback. It’s probably like with the other caching modules that wp_head is not being processed. I’ll try to look into it on the weekend.

    Plugin Author ti2m

    (@ti2m)

    I looked into w3 total cache. It seems to work for me though. w3 is to complex though to try to set the error off. Maybe you can try to deactivate some of the options. If you can narrow down what the issue might be in your case I can try to help.

    Thread Starter tallhat

    (@tallhat)

    thanks for looking ti2m. i’ll see if i can narrow anything down at my end.

    Plugin Author ti2m

    (@ti2m)

    Hi, is your site online anywhere? Otherwise sent me a dump of the source of a page where an edge animation should show up, then I can take a look. [email protected]

    Thread Starter tallhat

    (@tallhat)

    i’ve just discovered it’s the W3 minify option that’s the problem. i can run W3 with page, db and browser caches turned on, but if i use minify it kills the edge content.

    Plugin Author ti2m

    (@ti2m)

    That narrows it down a lot. The dump you sent also shows that the stage is being placed in the html. Can you activate the minification again, then I take a look at your page and check what’s going on. The console should throw errors.

    Plugin Author ti2m

    (@ti2m)

    Problem seems to be with AdobeEdge.pathPrefix.libs not being defined right away. This is probably because of shortcodes, I have to look into this in more detail.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Edge Suite and W3 Total Cache’ is closed to new replies.