-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Next: switch to pest, enable globals, fix errors/exception handling. #122
Conversation
@QWp6t: Great work! Has this already been released (acorn) and required by Sage 10? |
what issue? |
@Log1x: PHP notices and warnings causes a whoops error/exception that makes the whole page unusable. |
this should only happen on development. we could probably use an |
@Log1x: Good point. Though this also happens for me in production 😿 (blank page then, but corresponding error log entry). Relevant issue + workaround: |
is this primarily happening in admin? |
No, it also happens on frontend. But most PHP notices/warnings (e.g. WooCommerce) happen in admin, so I notice them mostly there. Well, so yes, primarily it is noticeable on admin. |
Closes #87
Closes #100
Closes #109
Closes #110
Closes #111
Closes #112
Closes #113