Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The attached patch cleans up the logging and alerts page. It simplifies the page title and the radio buttons for selecting the level of error reporting. Before and after screen shots:
Comment | File | Size | Author |
---|---|---|---|
#10 | logging_errors_cleanup_02.patch | 1.94 KB | Xano |
#5 | Screenshot.png | 15.34 KB | catch |
#5 | logging_errors_cleanup_01.patch | 1.95 KB | catch |
logging_errors_cleanup_00.patch | 1.94 KB | Xano | |
Comments
Comment #1
Xano/me blames teh
inputtext formats.Comment #2
Dave ReidI'm not sure this will be an improvement. Non-techie people will have no idea which setting they 'should' be in. -1
Comment #3
XanoWhat about this:
Personally, I hate telling people how to set up their sites, since it's none of my business.
Comment #4
XanoBojhan and I agree on the initial patch, although we need to think of a better description than "Functional errors only".
Comment #5
catchI'm fine with this if we have some kind of indication that the radio only affects what's displayed on the screen. How about this?
However, this could be in the title rather than the description.
Comment #6
XanoIs this really only about PHP errors?
Comment #7
catchYes.
Comment #8
XanoEverything passes and we agree on the patch, so this seems like an RTBC to me :)
Comment #9
Dries CreditAttribution: Dries commentedI disagree with this patch. "Site in development" is much more useful than "Functional errors only". Who is going to explain my mother what "functional errors" are?
Comment #10
XanoI checked common.inc and option 2 displays all messages except notices. Suggestion:
Since this is a developer's feature, I believe it's safe to assume that Dries' mother won't touch it if she doesn't understand the label and if she does, the options are pretty self-explanatory. Everybody who actually needs this setting will know what each option means. The only drawback is that
E_USER_NOTICE
will also be displayed, despite it's not an error or a warning, but we could fix this in another issue, since it seems like a bug to me.Comment #11
XanoComment #12
XanoKick.
Comment #13
catchI like #10.
Most of our mothers are either going to have sites set up for them, or be dealing only with a 'live' site on shared hosting - they're not going to be dealing with development / staging / live workflows at all, unless they happen to be web developers - so I don't think the extra text is helpful there.
Comment #14
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks!
Comment #15
Dave ReidI'm not sure I like the changed page title to 'Display PHP messages'. These messages could be database messages, not necessarily PHP. :/
Comment #16
Xano@Dries: Yay!
The page is about everything related to logging and alerts in Drupal. The setting about PHP messages is just about whether PHP messages and/or errors are displayed on the screen.
Comment #17
Dave ReidGot it. Could have just been "Display error messages", but overall a good change and glad it's been committed to core.
Comment #18
Xano"Display error messages" would have been a too general label, since this is stricly about PHP messages. There are other kinds of errors in Drupal as well.
Comment #20
Xano