Found a fix. Apparently CMB doesn’t use integers while saving values to database from custom checkboxes, but rather adds an on string when a checkbox is checked. Also when a previously checked checkbox is unchecked, the corresponding row isn’t removed from wp_postmeta table, but remains there with an empty value. So this will return all … Read more
Let me quote what’s mentioned in the official FAQ of WordPress.com Stats plugin (JetPack statistics module uses this plugin as the base)… The plugin collects stats via a javascript call, so as long as the JS call is on the page stats will be collected just fine, whether the page is cached or not. In … Read more
WP has multiple caching APIs really. For caching of data, that can be easily rebuilt, Transients API is typically used. However it’s up to you how to architecture interaction with your script. WP exposes Ajax endpoint but its performance is questionable if you need extremely fast responses.
The WordPress object cache isn’t a persistent cache, it’s meant to cache data within a single page load, so “as long as possible” will never be longer than a single request. Use the Transients API if you want to store your data across multiple page loads, or even simpler, just store it in an option … Read more
You could use Teleport or some other crawler to create a “proper” offline version of the website. However, if your client would want to showcase posting something or some other functionality that requires database interaction, then you’re far better off using a local installation on XAMPP or alternatives of it (enable Apache and MySQL to … Read more
WordPress doesn’t actively participate in the process of actually serving your stylesheet file. It links to it in page source, but as actual physical file the handling of it isn’t done by WordPress core and passed to the webserver to be served as any static file would be. ?ver=3.9.1 is added by default, if actual … Read more
This has nothing to do with caching, but with form auto-completion. It is happening because the browser is set to store form content. To avoid this, you should generate a random code and add it to the name attribute of your input tags. Then send the random generated number trough another hidden input so you … Read more
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 … Read more
Simplest way to see what is causing it is to disable all plugins and add them back one at a time. If that doesn’t reveal it, switch to a default theme. After that I’d say it is something server side. To answer your question though – caching should help but it depends on what is … Read more
I would suggest using nginx along with varnish. Varnish is a caching mechanism which runs on top of Apache/nginx. You can configure it to purge the cache after a specific time if you have users updating content often. In terms of server configuration, I would recommend Amazon Web Services’ EC2. This will allow you to … Read more