This code snippet will show you how you can disable caching of enqueued scripts in WordPress in your development/staging environment(s) but not in your production environment.
define( 'WP_ENV', 'development');
(replace ‘development’ with whatever label you want for each environment, such as ‘staging’, ‘production’, etc.)
We’re now going to tell our enqueued scripts to either:
It is rare that I find a plugin/framework that gets me so excited. One of these days I will have to publish a list of my favorites. Today I am here to talk about Carbon Fields for WordPress.
Let me begin by saying that Advanced Custom Fields Pro is one of my favorite plugins, and I probably use it more than any other (maybe on par with Redis Object Cache). I have a developer’s license for it. It is amazing and also a bargain! I wish that I could use it for everything!
That said, some of the things that make ACF Pro amazing, like Repeater field and Options pages, are not redistributable for free (as in beer) plugins. I totally understand and respect why – I would do the same thing. However, there are times when I make a plugin that I just want to give …
There are some simple, some free, some more difficult and some commercial solutions out there for making WordPress more secure. The question is not IF you will get hacked, but WHEN. The more you can do to secure your web site, the better.
Below are minimal steps that you should take to help secure WordPress, in order of importance: