--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
Great work on the nested themes, I like it.
I'm also in favor of dropping the theme-selector. I've never used
it in any project.
I guess it should be added to the subsites-module somehow. Since
subsites are created/administrated within the CMS, it does make
sense to have a theme-selector there… (as opposed to a
single-website, where the developer installs the theme and adjusts
the config file accordingly).
The available "themes" for the subsite module could also be
configured via config-api instead (so that the developer can
specify which "parts" form a theme?). Not sure how it would work
in detail, as I don't fully understand how the nested themes work
yet :)
@Mike: Just FYI: You can easily remove the theme-selector by creating a DataExtension for SiteConfig and add something like this to it:
public function updateCMSFields(FieldList $fields) { $fields->removeByName('Theme'); }- Roman
--