New answers tagged cache
I have faced similar issue while working for a client. The issue may cause due to following reasons. Check server configuration and server cache. ( This happens if you are using specialized wordpress hosting; the server admin configured some cache mechanism to increase performance) In this case you have to wait till the sever refresh its cache.
The solution is simple: Use the last time the file was changed as version number. You can use filemtime() (File Modified Time) on the path of the file. Example: wp_enqueue_style( 'your-handle', get_template_directory_uri().'/assets/style.css', # use plugin_dir_url( __FILE__ ) for plugins array( 'dependencies', ), # use  for PHP 5.4+ ...
4.1 is coming from your WordPress version. Also you should not append ver= to the src manually but use the fourth parameter of wp_enqueue_style.
try to remove ?ver= 4.1 is coming from wordpress, by default it set's a wordpress version
Yes, caching is a must to any site which expects some decent traffic. The hardware and software got better over the years but at some point you will need to use caching to improve you performance. caching can come is several flavors, caching of the php executable code, request caching at DB level, in memory caching of intermediate results, and full page ...
The mix up is usually because these extensions are about two unrelated technologies: opcode caching and key-value data store. For WordPress you prefereably want both. Opcode caching is really the "normal" way to run PHP (and lack of it is essentially crippled shared hosting way). Data store can *(and should) be used by WordPress object cache plugins for ...
Top 50 recent answers are included