Thread: Hooks and Child Theme in Wordpress 3.3.1 and Classipress 3.1.6/3.1.7

Hooks and Child Theme in Wordpress 3.3.1 and Classipress 3.1.6/3.1.7

Getting ready to start over with a clean install of Classipress 3.1.6 with Wordpress 3.3.1. But before starting work on the modifications that are on my current version of 3.0.5.3 site I need to know if I'm on the right track with my understanding of hooks and a child theme working together...The way I'm interpreting things is the more you can utilize the hooks the better, and use a child theme for things that are unlikely to change. From what I understand, if an update/upgrade changes anything that’s being handled by the child theme then creating a new child theme is recommended so that the update/upgrade change in the parent theme can used, otherwise you won’t see or be able to use the change because the child theme files is what gets looked at first on the site when it’s loaded. If using a hook for a modification, it can be unhooked if it’s no longer needed. So with that said, modifications should be sorted out in accordance to what will is believed will be best handled by hooks (meaning that anything that has the potential of being changed in a future update/upgrade should utilize the hooks), and anything that’s unlikely to change should be handled by the child theme. In regards to this thread http://forums.appthemes.com/duplicate-footer-25606/ there seems to be problems with getting hooks and a child theme to work together. It sounds as if there might be a fix to these issues in version 3.1.7...Can anyone confirm this? If there is a fix on the way in version 3.1.7 I will simply hold off on working on the modifications until its released. Any input on this would be greatly appreciated, as I want to make sure that I'm understanding everything correctly and that when working with the modifications, that their being done properly. I only have roughly maybe 12 mods, so I'm sure it's probably going easier for me than others who have many more modifications and will have to depend on either a child theme to handle them all or just put in them in the parent theme and redo them on every update. There seems to be confusion in other threads on this subject, so maybe this one can help clear some of it up.