The Gutenberg WordPress Editor will very soon be part of WordPress core. This new editor promises a completely different content creation experience in WordPress, and is arguably one of the biggest changes of functionality in WordPress history. And no single core feature has ever inspired such heated debate amongst WordPress users and developers.
Author: Jamie Schmid
Last weekend I had the opportunity to check out the Drupal community in San Diego, during the 10th annual SANDCamp. SiteLock protects many Drupal sites in addition to WordPress sites, so it was a joy to meet everyone in the community and learn more about the current state of Drupal.
In our series on managing WordPress updates, we’ve discussed how crappy it is when your website breaks, and examined lots of solutions to avoid it ever happening. One of the things we strongly recommend is having a good backup process in place.
We know updates are important! We also know updates can potentially break your site. When your LIVE SITE breaks, it’s a huge deal and can be time consuming and costly to fix – both in terms of technical support, and lost revenue. A much better solution is to first do your updates on a version of your site that ISN’T live, a site that is an exact duplicate of your live site. A site that can break without causing pandemonium in your life. This site is called a Staging Site, and it’s the recommended way to make updates and changes before doing them on Live.
Updates to your WordPress site become available all the time, whether these are updates to Core, Themes, or Plugins. Since many updates build off each other, the longer you wait to update, the greater the risk of something going wrong. Smaller incremental updates makes it easier to identify and fix an issue if there is one.
This is the second post in our series on managing WordPress updates. Without a good process in place to make sure updates are happening correctly, your site could be at risk of security vulnerabilities and outdated functionality. It’s easy to forget this part in your website business plan: when you go live, all of your themes, plugins, and WordPress core will be up to date running on the latest versions. But updates to everything from security patches to new features are constantly being published, and it’s important to stay on top of them.
It’s a tense moment: after a few months of ignoring that “Update WordPress” notification in your dashboard, you’ve finally decided to push the Update button. Which is it going to be? Success Upgrading WordPress! or… The White Screen of Death? You click UPDATE and hold your breath…
Not going to lie: I still hold my breath when I push that Update button. I’ve been building sites with WordPress for over 6 years now, I’m familiar with all my plugins, and keep informed of every update that happens with my theme. And yet, there’s always that little nagging doubt that something COULD go wrong. How do I REALLY know that this update isn’t going to break something?
This weekend I flew South to the desert and joined SiteLock in their hometown state for WordCamp Phoenix 2018! This camp comes less than 4 months after WCPHX 2017, as they will now be hosting WordCamp in late February instead of in the Fall. And somehow [as someone who has helped organize 2 WordCamps myself, I literally am in awe of this] they still managed to pull off another massive and beautifully orchestrated WordCamp. For those unaware, WordCamp Phoenix is consistently one of the largest WordCamps in the country alongside Miami, and this year boasted over 500 attendees with concurrent talks across 3 tracks during the Friday-Saturday weekend. SiteLock was there in October and we were back again last weekend for another awesome info-packed event!