My CDN or Cache Plugin can't cache these files

[Johnny]

http://gtmetrix.com/reports/tradr.com/46BGu8Zh

Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:

http://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.woff?v=4.3.0
http://tradr.com/wp-content/plugins/buddypress-global-search/assets/css/buddypress-global-search.min.css?ver=4.1.1
http://tradr.com/wp-content/plugins/buddypress-global-search/assets/css/jquery-ui.min.css?ver=4.1.1
http://tradr.com/wp-content/plugins/siteorigin-panels/css/front.css?ver=2.0.7
http://tradr.com/wp-content/themes/boss-child/css/custom.css?ver=4.1.1
http://tradr.com/wp-content/themes/boss/buddyboss-inc/buddyboss-slides/css/buddyboss-slides.css?ver=1.0.2
http://tradr.com/wp-content/themes/boss/css/bbpress.css?ver=1.0.6
http://tradr.com/wp-content/themes/boss/css/buddypress.css?ver=1.0.7
http://tradr.com/wp-content/themes/boss/css/plugins.css?ver=1.0.6
http://tradr.com/wp-content/themes/boss/css/wordpress.css?ver=1.0.6

Is there a reason why these static files need to have their version questioned every time they load?

Cheers,

Johnny

[Alyssa]

@johnny this is a WordPress thing. Perhaps this discussion will point you in the right direction: https://wordpress.org/support/topic/get-rid-of-ver-on-the-end-of-cssjs-files?replies=19

[Johnny]

Ok @tjchester

I have fixed everything, except:

GET http://tradr.com/wp-content/themes/boss/css/options.css?ver=2087611012

[Johnny]

Is this file meant to exist? I can’t find it in my parent or child theme folder.

[Alyssa]

@johnny it should exist in the parent theme, it appears it may only be created after you use the theme customizer. I’ll forward this to the dev team but in the mean time you can create an empty file called options.css in the theme css folder.

[Anonymous]

@johnny

The version enqueues are actually added specifically for caches and CDNs. Without that, the CDN will never know your file has been updated (with a theme update for example) and then it will constantly be serving stale files. Enqueuing the version number tells the CDN that the file is updated and then it is supposed to purge the cache for that file and regenerate it using the updated file. This is best practice and is very common. It’s the default WordPress method, but is also just standard across the web. If your CDN can’t handle a “?” I really suggest changing to another CDN (MaxCDN is awesome and cheap) because tons of resources on the web use “?” to add version numbers, it’s extremely common.

Is this file meant to exist? I can’t find it in my parent or child theme folder.

This file is created when you first save something at Appearance > Customize. The theme does not ship with the file. If it did, every time we push an update your existing customizer settings would get overwritten by the update. The enqueue at the end is a random string of numbers, which is changed every time you change a setting in the Customizer. This ensures that your CDN and any caching plugins know to purge the cache on the file and server your latest version reflecting all changes in the customizer.

Hope this helps. Again, a simple solution is just to switch to MaxCDN or another CDN. This is not an issue I have ever seen before…