Fixing something is often not enough, even though in feels like that in the front-end. You have to look in perspective as other developers could work on the website and one needs to make it as developer friendly as possible.
Whenever I’m into WordPress troubleshooting, I make sure of the following:
- The changes I made are according to the WordPress Coding Standards and the way the Theme is setup. For instance, if I want to modify my current website’s theme, which is powered by the well know Genesis Framework by StudioPress, I’m following their documentation to ensure everything is properly organised and remains developer friendly, fast in loading and secure.
- I do not touch any of the WordPress core files, plugin files or any other files within the theme that are likely to require updates in the future. Imagine fixing a bug or making a custom change to a WordPress plugin that needs to be updated to a newer version later. You don’t want to mess with that. There are exceptions but these are rare and any change should be properly documented.
Before starting to fix your website, I’d need:
- A detailed description of your problem
- Your WordPress website URL
- Dashboard Login Details of an Administrator Account (yours or one created for me)
- FTP Login to your website
- Control Panel access to your website (if possible, not a must)
As plenty of my customers were most of the time curios what was wrong and what changes I’ve made to take care of the issue, I will provide you, if you wish, all the changes I made including number of files changed, database alterations etc.