A problem with this module is causing the debug.css file to used on the CMS Pages (edit) interface which in turn causes styling issues
Steps to reproduce
Login to the CMS (admin/)
Travel to the Pages section using the left hand navigation (admin/pages/)
Click on one of your pages in the Sitetree to edit it (admin/pages/edit/show/1)
Look closely at the styles of the CMS interface
Screenshots
Before Installation
Here is how the CMS Pages edit interface should look (in SS4)
After Installation
And here is what it currently looks like (some styling issues are highlighted in yellow).
The most noticeable difference is the font size and the left hand menu (which has items jutting out)
The Stylesheet causing the issue
You can see that the debug.css file is being included. If you disable its styles using the developer tools the styling issues will be fixed.
Possible Explanation
I originally brought this problem up over in the Silverstripe Slack channel (see this conversation) because I thought that it may be a framework bug (because debug.css is from the silverstripe framework). However when I discussed this issue with Andy he explained to me that this stylesheet is only included when the debug class (SilverStripe\Dev\Debug) is included or when an error has occurred.
The Problem
A problem with this module is causing the
debug.css
file to used on the CMS Pages (edit) interface which in turn causes styling issuesSteps to reproduce
Screenshots
Before Installation
Here is how the CMS Pages edit interface should look (in SS4)
After Installation
And here is what it currently looks like (some styling issues are highlighted in yellow). The most noticeable difference is the font size and the left hand menu (which has items jutting out)
The Stylesheet causing the issue
You can see that the
debug.css
file is being included. If you disable its styles using the developer tools the styling issues will be fixed.Possible Explanation
I originally brought this problem up over in the Silverstripe Slack channel (see this conversation) because I thought that it may be a framework bug (because
debug.css
is from the silverstripe framework). However when I discussed this issue with Andy he explained to me that this stylesheet is only included when the debug class (SilverStripe\Dev\Debug
) is included or when an error has occurred.