-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whoops! Stack trace styling gone wonky. #4715
Comments
This is on purpose. This is the original whoops styling, and custom Laravel styling has been removed for maintainability. |
Oh, well that is understandable, if not a bit disappointing. The custom Laravel styling was a really polished element, albeit seen by very few people I guess. Was there an announcement or some in the change logs that I missed? |
See the discussion here: #4378 (comment) |
Yes, I'd seen that discussion as of a few minutes ago. Thank you for following up. |
@tonydew If you want the orange color and old font size, here is my repo with css, I`ll update it on whoops updates.
DefaultOld (orange) |
Hey! Cool. Thank you. |
After a
composer update
earlier today, the Whoops! stack trace changed appearance:While troubleshooting, I ran
artisan cache:clear
andartisan clear-compiled
but had no luck. Still blue. Then I set composer.json to require "laravel/framework": "4.2.0" and did anothercomposer update
and thenartisan cache:clear
andartisan clear-compiled
All good! Got the cool orange styling back. So then, I stepped through each iteration. 4.2.1 is fine. Then 4.2.2 looks like this:
Then 4.2.3 goes back to looking like the slightly unfinished blue colored one.
Looks like there has been some work to clean Remove some unnecessary Whoops files. recently. Maybe were a little more necessary than first thought?
I know it's just styling, but I thought you'd like to know.
The text was updated successfully, but these errors were encountered: