Closed boywondercreative closed 10 years ago
Hi @boywondercreative,
the actual update from 3.1.0.2 to 3.2.xx won't break your installation, although it is proposed to export your theme options firstly, just in case. About customizations and child-themes, we created a file with all deprecated actions & filters in /lib/deprecated.php, BUT it is recommended to re-write your stuff with the new OOP way of Shoestrap core. You can always give a try though to see if the 'deprecated' file do its magic! :p About WP compatibility, we're always using the latest, and even beta, versions with the current latest Shoestrap version we're working on (that's the master branch most of the times), so can't promise about future compatibility for a deprecated version like 3.1.0.2.
Waddup aristath, fovoc, dovyp,
I see you guys showing off the Foundation integration on the new documentation site. I also read about the deprecated functions/actions, and know that upgrading from
3.1.0.2 to 3.2.3 will break I have in development using a child theme.
What concerns should I have if I choose to use 3.1.0.2 as my parent theme for the next 10 - 20 years?
Kidding. But of course clients will wonder about compatibility issues with future versions of WP.
anyways, props dudes, sc