Support » Plugin: Awebsome! Browser Selector » WP Supercache compatible?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Raul Illana

    (@raulillana)

    Hi mate!

    It works fine for all my installs (about +200) with W3TC, and I had no other complains about this, so…

    Drop me a line if it’s not working with WPSC and I’ll try to fix it.

    Best!
    R

    G’Day

    Any news on whether it is compatible with WP Super Cache or Hyper Cache?

    Thanks

    Plugin Author Raul Illana

    (@raulillana)

    Hi haleeben.

    As I said up, no complaints until now.

    So if you’re so kind, please give it a try and let us know your feedback. 😉

    Best!
    R

    Hey Raul
    I gave it try with WP Super Cache and it doesn’t work, it stores the class name’s for the browser when the page is cached.
    I tried with W3TC using the Page Cache setting enabled and it didn’t work, it did the same thing.
    bummer 🙁

    Plugin Author Raul Illana

    (@raulillana)

    Hi again haleeben.

    As I said, +200 blogs on W3TC + Varnish working with no problems actually.

    Here, some sites on our network to check out (as you can see, the body tags change for each browser, so I’m pretty sure no JS needed for this as @jrevillini patched):

    Anyway, take care that W3TC does not work with shared hostings (and also with local ones, imo). Maybe that’s why you can’t get it to work?

    In other hand, as I understand how the cache works, the page is firstly created from scratch and then cached the first time you open it, so the classes are applied before the cache creates it.

    Must say that this is a mess. That’s why default themes use in-theme filters. :\

    PS: Remember there’s a bug with IE not working that will be fixed, hoping I get time, this weekend.

    Best!
    R

    I’ve written an add-on plugin that gets installed side-by-side with ABS to overcome caching issues. Mine is called Awebsome Browser Selector for CACHING.

    Raul, I know you don’t think a JS solution is necessary, but I can tell you from experience and haleeben’s testimony: ABS doesn’t work with WP Super Cache and anything that caches and serves the entire page.

    My guess is that it depends which type of caching you employ. Even with W3TC, if you turn on page caching (there is also JS and CSS caching), there are documented issues with dynamic body classes[1][2].

    Varnish is a whole different animal. It’s extremely advanced and does have ways to do per-user-agent caching, but it needs to be set up[3].

    I posit that my plugin is the fastest and easiest way to configure ABS to work on a site that employs page caching.

    Hey James

    Looking forward to trying it out.

    Thanks

    1. Make sure you get 1.0.2 as there was an issue with the AJAX call in 1.0.1
    2. Make sure you clear your WP cache one time after installation of my plugin, just to be sure that my code is run to add some JS to the <head>.

    Please post your results!

    Hey James

    From my testing so far it works great, great job.

    Thanks. Please rate the plugin if you have a second.

    Plugin Author Raul Illana

    (@raulillana)

    Hey people.

    Cool. I’ve noticed we’re not caching with W3TC really.

    I’m very bussy right now, but I’ll take a look to include it again in a new release.

    Best!
    R

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘WP Supercache compatible?’ is closed to new replies.