Over the last few weeks we’ve published a couple nifty updates for our themes running the Bean Framework version 2.0+. This is just a quick run-through of a couple of the key new features.
As a quick reference point, you may have noticed the
bean_feature_setup function at the top of your theme’s functions.php file. Within this function there are a few true/false statements – set to activate or deactivate various forms of functionality within the theme. I recommend that you’ve installed the child theme included within your theme package files, activate it – then modify a functions.php file within that child theme (using that function).
This week we are pushing updates to all our themes running 2.0+ with a functions.php file already included/set up in the provided child theme.
1. Theme Update System.
Another new feature that we’ve added to the 2.0 themes is a fully functional theme update notification & install system. If enabled, our themes will perform exactly like themes downloaded from the WordPress theme repository. Site administrators will be notified of available updates and presented with the option to apply the update from within your WordPress dashboard.
Please note that any modifications to the theme’s core files WILL be overwritten upon updating your theme. To ensure your custom code/assets are not deleted, I recommend using the included child theme within your theme’s package. Apply your custom CSS, functions, assets, and template files there and your changes will be a-okay.
As some users would prefer not to employ the update system, it may be activated/deactivated within the
bean_feature_setup function, in the primary – updates key.
2. Theme Whitelabeling.
As part of our v2.0.5 Bean Framework push, we’ve added an option to completely whitelabel the theme framework. If the whitelabel value is set to
true– within the
bean_feature_setup function – the default ThemeBeans favicon, logo and general references to ThemeBeans will be removed. This is a great addition those developers out there who are customizing our themes for clients – and now there’s no need to dive in and “rip” out code.
We’re consistently working to make our framework better for all. If you have any suggestions or ideas for future implementation – I’d love to hear them.