For reference, r4916 and r4917 remove the <class> requirements. So, if you didn't heed the instructions above your themes will no longer be broken.
You still should remove any defined THEME_CLASS from your theme.php. This change has also already made it into the 0.7 release candidate 2. On Feb 12, 8:25 pm, mikelietz <[email protected]> wrote: > I have committed r4875 which breaks all non-core themes. > > Fortunately it's an easy fix. > > Add a <class>Classname</class> to the theme.xml file, where Classname > matches the one in theme.php (in this case you would see class > Classname extends Theme { ....). > > Now, you might ask *why* this was done. Prior to r4853 and r4875, > themes and plugins could not react to theme activation or > deactivation. Now they can. > > Now, you can register action_theme_activated() in the theme.php to > create some content, or set some settings, or make some blocks. I've > built a number of sites that included a special page template to > import some data because I didn't have this capability before. > > Likewise, you can use action_theme_deactivated() to clean things up > when a theme is deactivated. > > For a plugin, use action_theme_(de)activated_any. > > This change means THEME_CLASS does not need to be defined in theme.php > files (and in fact having that there was one part of why such hooks > couldn't exist). I plan to update the themes in -extras to have these > defined still so they remain compatible with 0.7dp3 and trunk prior to > r4875, but once 0.7 is released these define()s are no longer needed. > > Right now if you svn up with a non-core theme it will remain active, > but site output will most likely be affected. Again, it's an easy fix, > and really, it's all for the better. > > mikelietz -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users
