Attention: anyone using a child theme with ClassiPress or developers that have created a child theme for ClassiPress should absolutely read this post!
While we strive to implement these changes with minimal impact, there are some changes that are going to require a little extra work on your part when you update to newer versions. With ClassiPress 3.2 on the way, we want to give everyone ample opportunity to prepare for changes that might have an impact on your site.
Our ClassiPress developer, Andrzej Piotrowski has created a checklist of debugging tasks for anyone that uses or has developed child themes for ClassiPress. The list is pretty short and should not take too long to complete. Once you complete the tasks, you should be in pretty good shape for the official release of ClassiPress 3.2.
How Do I Know if I Need to Make Changes?
If you’re not a developer, you might be thinking, “oh my gosh, I have no idea what I’m supposed to do!” Worry not, this tutorial is mostly for advanced users and developers. Just to be sure, here are some simple guidelines to determine if the changes mentioned above will affect you:
- If you’re a novice user – you’re not a developer – and you bought and simply installed ClassiPress on your site, you probably do not need to do anything.
- If you bought and installed a child theme, you will want to contact the developer of your child theme and ask them what their plans are for updating.
- If you hired a developer to modify your theme in any way, you will want to contact that developer and direct them to the checklist.
- If you have created a child theme or modified the theme code in any way (not recommended), then you really should read the checklist.
Suggest a Tutorial
Child themes and custom things. Action hooks and custom looks. Plugins, filters, PHP. We provide these tuts to you for free! Tell us in the comments what you want to see.