Hi guys!
Why do you use require_once (a) to load framework files instead get_template_part (b)?
a) require_once TEMPLATEPATH .”/framework/class/class_widgets.php”;
b) get_template_part( ‘framework/class/class_widgets’ );
If you’d use get_template_part, framework classes could be customized easier by child themes.
Why don’t you allow to customize core files? https://www.premiumpress.com/forums/topic/customized-core-files-not-working-in-child-theme/#post-27931
I know (almost) everything can be done with the Actions & Filters API https://www.premiumpress.com/forums/topic/customized-core-files-not-working-in-child-theme/#post-27938, but this little change (using get_template_part) could do everything easier, and that way we can choose when to use hooks and when to overwrite core files. Remember, WordPress child themes are meant to overwrite parent functionality.
Thanks
This reply is for PremiumPress customers only.
593
Views
2
Replies
Copyright © 2010-2026 PremiumPress Limited.
Hi guys!
Why do you use require_once (a) to load framework files instead get_template_part (b)?
a) require_once TEMPLATEPATH .”/framework/class/class_widgets.php”;
b) get_template_part( ‘framework/class/class_widgets’ );
If you’d use get_template_part, framework classes could be customized easier by child themes.
Why don’t you allow to customize core files? https://www.premiumpress.com/forums/topic/customized-core-files-not-working-in-child-theme/#post-27931
I know (almost) everything can be done with the Actions & Filters API https://www.premiumpress.com/forums/topic/customized-core-files-not-working-in-child-theme/#post-27938, but this little change (using get_template_part) could do everything easier, and that way we can choose when to use hooks and when to overwrite core files. Remember, WordPress child themes are meant to overwrite parent functionality.
Thanks
Members Only Content
This reply is for PremiumPress customers only.
Login NowMembers Only Content
This reply is for PremiumPress customers only.
Login Now