Building a WordPress theme can seem like a daunting task, but with the right tools and guidance, anyone can do it. Here is a step-by-step guide to help you create your own custom WordPress theme:   Step 1. Plan Your Design: Before you start coding, plan out your design. Consider your site’s layout, color scheme, typography, and other design elements. Sketch out your design or use a tool like Adobe XD or Sketch to create a mockup.   Step 2. Set Up a Development Environment: You will need a development environment on your computer to build a WordPress theme. You can use either WAMP, MAMP, or XAMPP to set up a local server environment.   Step 3. Create a New Theme Folder: In your WordPress installation, go to wp-content/themes and create a new folder for your theme. Name it something unique, like “my-custom-theme”.   Step 4. Create the Necessary Theme Files: Inside your theme folder, create the necessary files for

WordPress is one of the most widely used content management systems for building websites. One of the reasons for its popularity is the vast collection of plugins available that extend its functionality. If you want to add a specific functionality to your WordPress website, you can either look for a plugin that does that or build your own. Building your own plugin may seem daunting at first, but it’s not as difficult as it sounds. In this blog post, I’ll guide you through the steps of building a basic WordPress plugin.   Step 1: Set up your environment Before you start building your plugin, you need to set up your development environment. You’ll need a local installation of WordPress on your computer. You can use tools like XAMPP, WAMP, or MAMP to create a local server environment on your computer. Once you have WordPress installed, you can create a new folder in the ‘wp-content/plugins’ directory and name it after your

Recently, a client of mine running eCommerce on WordPress was faced with a bit of a dilemma. Due to a plugin conflict, their error log file grows at a staggering rate, eventually consuming all available disk space and crashing their site. I know as a developer, my first step when they reached out to me was to check the error logs. The first time I checked, the log file was over 80GB! Let’s talk a bit more about the setup here. They host with Codero on a VPS and manage everything through PLESK (gross). They run WordPress with WooCommerce. We had to take a phased approach here to solve the problem. I’ll be talking about phase one: Create a job to remove the error_log every 3 days. That’s the scope right there. Pretty simple! It doesn’t fix the overall issue: Why is the error log filling up so, much so fast? That’s my next phase (another day). Okay, let’s explain

Laravel has great documentation which is only one reason I love working with it so much. With that said, it has some dependencies that require a bit of research and configuration to get it installed. With a little bit of trial and error (and Google) I was able to get it set up. The issues that I had were mostly because of the host, not Laravel itself. Others may not have the same issue that I had, but I’ll walk through what I needed to to to get it up and running. INSTALLATION Laravel utilizes composer to install/run. Composer documentation explains two ways to install. curl -sS | php or php -r “readfile(‘’);” | php I had issues with both because every time I tried to run the command, I’d get an error saying I was running php 5.2.17. Running php -v showed exactly that. Now, I know when I set up the hosting for the domain I selected PHP 5.6