You get a WordPress error that says, "HTTP Loopback Connections Disabled."
It took me awhile to figure this one out. I was getting it on a BuddyPress install (and other have reported seeing it with BackupBuddy, among others).
Most of the web sites had pointless or ineffective solutions. Some said to add define('ALTERNATE_WP_CRON', true); to wp-config.php, which was completely irrelevant, uneffective and annoying.
This is what worked for me.
I was working on a client site and was wondering about similar impact that my optimizations would have on a cloud instance with even traffic (read: zero traffic). I tested various things on a demo site that I set up for a client. I thought that the results were interesting, so I thought that I'd share.
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.
Add Environment Variable
- Edit the wp-config.php for each of your instances.
- Add the following (if it doesn’t already exist):
define( 'WP_ENV', 'development');
(replace ‘development’ with whatever label you want for each environment, such as ‘staging’, ‘production’, etc.)
Add/Modify Code to Enqueue Your Custom Scripts
We’re now going to tell our enqueued scripts to either:
- If WP_ENV is ‘production’, when append the theme version to the script.
- If WP_ENV is anything else (like ‘development’ or ‘staging’), append a timestamp to the script link.
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 …
Over the years, I have used several dedicated and cloud hosting companies. I thought that I would share my opinions on them (as far as the features that I’ve used among them).
Although I have tried Microsoft Azure and the Google Cloud Platform, I preferred the interface of AWS and/or the price of other options, so I did not give them much of a trial. As a result, they will not be included much in this article. I also do not have a DevOps background so I will not be discussing HA or load balancing a lot.
Amazon Web Services (AWS)
I used to be a die-hard promoter of AWS (I still use them for some of their specialty services, and recommend them depending on infrastructure needs).
- Speed – I have always gotten impressive transfer speeds while using Amazon’s
I just received my new MST3k pillow cases. You will be greeted by them when you visit my next apartment.
I have to get new pillows for them though. These didn’t fit right and were different sizes. I just used whatever I could find around the house.
I’ve tried several of the video streaming devices on the market and I thought that I would share my recommendations for those in the market for one.
Units that I have tried include:
Amazon Fire TV
Price: $49 and up
I was excited when the Amazon Fire TV came out. At the time, I was an exclusive Roku user, but Roku had not updated their units in quite some time and they were beginning to feel sluggish. The Fire TV promised a significant speed boost, and it delivered in that respect. However, it was disappointing for other reasons.
- Speed – The unit was pleasantly fast.
- Vendors – Supports Amazon Instant video and Prime
- Voice – It was the first streaming unit (to my knowledge) that offered voice commands.
- Apps – It supports most
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:
- Keep WordPress, plugins and themes updated – There are a number of ways that you can do this:
- If you are working with a web site that isn’t too complex and/or doesn’t need to be babysat, WP Update Settings is a great plugin. It allows you to configure what to update: WordPress minor updates, major update, plugins and/or themes. It also has the option to notify you of updates. Configure as needed.
- You can update your plugins manually if you prefer. It may help to use a monitoring services
I’ve seen a lot of sites that don’t use HTTPS by default. I’ve heard the argument, “We don’t need it. We’re not e-commerce.” This is absurd thinking:
- You are probably using some sort of CMS product, possible a popular one like WordPress, Magento, Joomla, etc.
- There is a good chance that you are not keeping them as updated as you should, but for arguments sake, let’s assume that you are (or pretend to be).
- All of these products have default administrative login paths. If you monitor your logs, you will notice that bots from all over the world are hitting this default path constantly.
Read more: Why HTTPS? Here Are the 5 Reasons Folks
Step 1: Change your default admin path!
If you are on WordPress, there are several …
This situation happens to me all the time. I'm working on a client web site, making updates or content changes, but the site is not responsive and/or wasn't built with any sort of CSS framework. I also encounter this problem when trying to throw together pages for the WordPress admin. I could do the work manually, but I've become spoiled by grids.
If I include the regular Bootstrap distribution, I have the problem of it changing style and typography. That won't work. I could use a different, grid-only framework, but I have become used to Bootstrap conventions.
To solve this problem, I simply compile the Bootstrap SASS files, including only the grid and responsive utilities modules. To avoid potential conflicts with other CSS, I use a wrapper (in this case, .bootstrap-wrapper). Now, I can simply include the CSS file in the project and use the syntax that I am so accustomed to.
This guide gives step-by-step instructions for installing Node.js, Nginx, PHP 5.6 and MongoDB on an Amazon EC2 instance. If you notice any errors, changes or have suggestions for alternatives/clarifications, please let me know.
This guide assumes that you are familiar with Amazon Web Services and using the Linux command line. This guide also assumes that you are performing these tasks on a fresh Amazon Linux AMI instance.