• Resolved webaware

    (@webaware)


    G’day again,

    Because I’m peering closely at the output of a new custom theme, I just noticed that EM and EM-Pro scripts and styles are all being enqueued with the default version string, being the WordPress version number. This could cause some people a little grief if scripts / styles are cached by visitors (or admins) and thus get out of synch with the PHP (or AJAX back-ends) they are supporting.

    I’d suggest you use EM_VERSION and EM_PRO_MIN_VERSION version strings, which will act as cache busters when new versions are installed.

    cheers,
    Ross

    http://ww.wp.xz.cn/extend/plugins/events-manager/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support angelo_nwl

    (@angelo_nwl)

    thanks for this, we will going to look into this.

    Plugin Author Marcus (aka @msykes)

    (@netweblogic)

    funnily enough, I’m just about done with a big change to how the event booking tickets ui works (getting rid of the jquery dialog), and I was thinking of going that way.

    sadly, this isn’t 100% reliable though, e.g. cloudfront doesn’t take querystrings into account for js files, but hopefully it’ll help!

    Thread Starter webaware

    (@webaware)

    G’day Marcus,

    That’s true about CloudFront only if you configure it to not forward query strings. Frankly, anyone setting it up like that deserves to get caching problems 🙂

    Remember, cache invalidation is one of the two hardest problems in computing science, the others being naming things, and off-by-one errors…

    cheers,
    Ross

    Plugin Author Marcus (aka @msykes)

    (@netweblogic)

    afaik that’s the default setup.

    Based on that, I’m guessing in most cases ppl don’t bother since it’s the default setting in CF (I must admit, on many sites I don’t either :)).

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

The topic ‘Enqueued scripts / styles getting WordPress version’ is closed to new replies.