• Skip to primary navigation
  • Skip to main content
  • Skip to footer

The WP Steward

Treating Your Site Like Our Own

  • About Us
  • Blog
  • WordPress Hosting

affiliate, tech support, vocation / November 23, 2015

Beginner Mistakes in WordPress: not using a Staging Site.

Easily a top-ten mistake I see beginner WordPress users making is updating plugins, themes, and other code on the live site. Updating your code on the live site, without checking to see if it’s going to break stuff, is what developers call “Cowboy Coding,” and it’s an epidemic among beginners.

If you update it on the live site, and it breaks things, what are you going to do?

I’ll answer that: you’re going to have a broken website, and a painful day of getting things back like they were.

jesse petersen please tell me you didn't just cowboy code.
Not a developer? You have an excuse, but only until you read this article. (note that the url in the image is no longer active.)

“But wait,” you say! “How can we update the plugin on a live site without clicking ‘update’?!?!”

Allow me to introduce you to the concept of staging sites.

A staging site gives you a duplicate site, often on a different server, for testing purposes. You create the staging site, make any changes and updates you want, ensure that those changes and updates don’t break the site, and then migrate the changes to your live site.

Up until a few weeks ago, any time I wanted to create a staging site, I did it manually. Most of the time I created the staging “server” on my local machine using a virtualization program to simulate a server here. I personally use VVV (Varying Vagrant Vagrants) and the VV extension by @bradparbs for creating staging sites. (sidenote, developers are bad at naming things. Hashtag VVVVV) I’ve also, for some more complex client needs, spun up separate DigitalOcean droplets as staging servers. Because they are paying me enough, it was worth spending the 45 minutes getting the staging server set up exactly with the same configurations as their live site.

For someone not comfortable with the command line, or without some server savvy, manually creating staging sites is not practical.

Until now.

WP Stagecoach is a company aiming to take the hassle out of creating and maintaining staging sites for your WordPress website. It’s a one-click process to spin up a staging site using WP Stagecoach.

Looking to take the stress out of WordPress updates? Try @WPStagecoach and relax! Click To TweetI’m not exaggerating when I say that on a recent Monday morning I used WP Stagecoach to update 5 different client staging sites in less than 30 minutes. I had a couple of minor issues with one of them that took an extra 10 minutes to sort out, or I’d have been able to do it in 20 minutes on all 5 sites. That’s including updating plugins and themes on the staging site and pushing them back to the live site.

Full disclosure: I not only like them as a company because of their product, I like them as people. Jonathan Kay, the founder of WP Stagecoach, came and spoke at WordCamp Raleigh 2015 (where I am an organizer), and ended up staying at my house!

As an aside: if your open source software hasn’t led to strangers staying in your house, maybe it’s time to switch to WordPress.

In addition to being the type of guy you let sleep in your guest bed, Jonathan is a top-tier sysadmin and developer.

So, if you are looking for a way to level up your WordPress site, and take the anxiety out of plugin updates, theme updates, or redesigns, take a look at WP Stagecoach.

Also, you’re darn right those are affiliate links. I love making money off of awesome products, and if you use one of the links above, I get a small percentage of the sale as a commission. And you get the freedom to update your site without fear.

Filed Under: affiliate, tech support, vocation Tagged With: wpsteward

Reader Interactions

Trackbacks

  1. Beginner Mistakes in WordPress: not using a Staging Site. | The WordPress C(h)ronicle says:
    November 23, 2015 at 10:30 am

    […] visit Benandjacq […]

  2. Update Your Site To WordPress 4.4, like a Pro. | BenandJacq in the Browser says:
    December 14, 2015 at 10:38 am

    […] to keep sites up and secure, not to be the first to get updated. My workflow for clients will be to set up a staging site for them, then to update to 4.4, make sure nothing breaks, and then to import those changes to the live […]

  3. Sometimes it pays to Cowboy Code. | BenandJacq in the Browser says:
    December 21, 2015 at 7:32 am

    […] I am working on client sites, I am beyond careful to never code on the live site, and to have multiple redundant backups, so that no matter how routine a task is, if it breaks […]

  4. What Icy Roads Reminded Me about Web Coding | BenandJacq in the Browser says:
    January 25, 2016 at 8:36 am

    […] know better than to code on the live site. I know that when coding on the live site, even tiny changes can risk purpling everything. The live […]

  5. Beginner Mistakes in WordPress: not using a Staging Site. - BenandJacq in the Browser says:
    March 14, 2016 at 10:23 pm

    […] Read the rest of this post over at the brand-new WP Steward Blog […]

  6. Themes Vs. Plugins: Which should Do What? says:
    March 23, 2016 at 12:32 pm

    […] change design and plugins change functionality. I should hypothetically (and of course never on the live site) be able to change my theme on a whim and not lose anything in the shuffle. Things like shortcodes […]

Footer

Get in touch

contact@wpsteward.com

© 2022 · Proudly Owned and Operated by Ben and Jacq, Inc. · Built on the Genesis Framework
Supercharged by the team over at Easy Digital Downloads

  • About Us
  • Blog
  • WordPress Hosting