WordPress is flexible enough to create just about any type of website. It’s also incredibly easy to use, which means the technical knowledge for getting started is pretty low. However, because of this, when issues occur (such as inevitable performance drops) you can be left waving the white flag.
Fortunately, there are a few steps you can take to preemptively minimize any serious harm.
Powering over 76 million websites and holding a 59% CMS market share, WordPress continues to dominate the web in 2017. However, with the new year comes new challenges. Since PHP 7 could be the minimum requirement for running self-hosted WordPress in 2017, updating your server’s version of PHP to PHP 7 could be a necessary step.
Without a WordPress theme framework, theme development and maintenance could be a major endeavor. Designing a website and customizing a theme – not to mention staying on top of security and Search Engine Optimization (SEO) – isn’t always a cakewalk.
Simply put, theme frameworks are akin to a starter culture. They feature essential core functionality, and give developers the flexibility to design without worrying about building a foundation with poor coding practices.
Nonces are an important part of WordPress security, but they are often misunderstood or misused. They are a key part of what authorizes an HTTP request to your site, which works to keep your code secure.
In this article, you’ll learn what nonces are, what a WordPress nonce is, how they can protect against certain types of attacks,
Lately, I’ve written extensively about object-oriented PHP, from class inheritance and visibility, to design patterns and magic methods. In all of these discussions, I’ve talked about classes without taking into account object interfaces.
Interfaces, often referred to as contracts or agreements, set up rules for classes in which a class that implements an interface has to follow those specific rules.
