Message of the day:
Release 4.5.0 is out. Changelog: https://docs.silverstripe.org/en/4/changelogs/4.5.0
SilverStripe 4 related information and questions.
which is mildly annoying but i at least understand
doesn't really explain the content_css thing - went down the rabbit hole a bit
It sounds like this is a bug introduced by the microtheme stuff. For the WYSIGWYG editor we should be pulling in the original theme.
@andante can you load the details of the bug into GitHub? I assume the issue is that the wrong editor.css is loaded?
the issue appears to be that it's not falling through to pick up the themes, so it only adds in the default
Perhaps the assumption was that themes should only be for the frontend?
might've been the other way, themes were developed with only the backend in mind?
Welp, looks like I'm adding