-
Notifications
You must be signed in to change notification settings - Fork 633
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
Feature Request: devMode per user #4765
Comments
“Dev Mode” is really just the Craft name for the YII_DEBUG constant, which needs to be set very early on in the application bootstrap phase, well before we can find out if someone is logged in. So this isn’t possible unfortunately. |
@brandonkelly Whilst that may be true I think there is a middle ground. Obviously, you can use the debug toolbar on the Frontend to find errors when they pop up in production. However, the "Dev Mode` error view is far better IMO. @tim-pixeldeluxe 's underlying issue was specifically focusing on debugging in production. If an error happens there you get a pretty vague My suggestion is this: Add an option to display the Overriding Already played around with this a bit so happy to submit a proposal PR for |
Yeah that wouldn’t hurt. |
Sorry, forgot to update this issue, but what @gtettelaar suggested/PR’d has been implemented for 3.3. |
You should be able to enable devMode per user and globally using the general config. You would enable devMode from the user preferences tab, the same way you enable the Yii debug bar.
This is especially useful when trying to find the cause of an error on your production env without having to enable devMode. Because sometimes you encounter errors on your production site which you cannot reproduce locally.
The text was updated successfully, but these errors were encountered: