Affects Version/s: 5.1.1
Fix Version/s: 5.1.2
A common complaint/request/pleading we've had has been to have a mid-level theme that provides very very basic styling to build themes from. Right now, _styled is essentially the exact same as Classic. However, every time we update Classic, we have to update _styled as well, meaning peoples themes break.
We've now abstracted out the main changes of what Classic is into it's own custom.css, and _styled is now a very basic barebones theme that maintains the necessary structure so people don't have to constantly redo the common stuff, while leaving out the extra styling that only the Classic theme needs.
This means that users won't have to constantly worry about themes completely breaking between releases. _styled will now mainly contain either just bug fixes, or portable feature additions that aren't only put in because Classic needs styling.
Since many people have already converted their current theme to run off of Classic in 5.1, there are two options.
One is to redo the theme to actually run off of _styled, which is the best long term. But if they would rather just rebuild their theme and not worry about that, and want it to the be the same, they can change the "theme.parent" setting to point it to use Classic as it's base.
The way they would do this is in their theme's build.xml, it normally looks something like this:
<project name="theme" basedir="." default="deploy">
<import file="../build-common-theme.xml" />
<property name="theme.parent" value="_styled" />
They just need to change the value of the theme.parent node from _styled to Classic.
That will fix any issues they have in the interim.