We have moved to GitHub Issues
Created by Morten Christensen 12 Jul 2012, 13:00:53 Updated by Simon Dingley 06 Jun 2016, 11:57:51
Is duplicated by: U4-683
Relates to: U4-8564
Relates to: U4-683
Relates to: U4-934
Subtask of: U4-5830
Stylesheets should only need to be stored on the file system.
Just like we did for the trees, have a fallback to the database still in place until we can actually remove the tables in a major release.
Moving this to 6.0.0 as we are running into time constraints and this could easily introduce an unnecessary breaking change (which we can work around, but that workaround would only live for two months so it's extra time/work for very little gain).
Marked as breaking because:
@Shandem How does/will this affect the RTE Formats dropdown?
It won't, it will still be the same, we just don't look for it in the db. The stylesheet properties in the file will be formatted so we can parse them. These properties will be appended to the file in the upgrade process
@Shandem Oh ok that sounds great, thanks. This is good news as I've currently had to expand the (relatively small) DB limit imposed on the style rules.
Will this allow us to use sub folders when creating CSS files in the same way that we can with partial views?
We can probably do that, but that functionality is not automatically included with this bug being fixed. You can submit a feature request for that or link to an existing one here if you want.
Assignee: Shannon Deminick
Backwards Compatible: False
Due in version: 7.3.0