[wp-trac] [WordPress Trac] #61391: Maintenance Error on Login After Setting Up WordPress 6.6 Beta 1 on Localhost

[WordPress Trac]

#61391: Maintenance Error on Login After Setting Up WordPress 6.6 Beta 1 on
Localhost
---------------------------------------------+-----------------------------
 Reporter:  nithi22                          |       Owner:  (none)
     Type:  defect (bug)                     |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.7
Component:  Upgrade/Install                  |     Version:  6.6
 Severity:  critical                         |  Resolution:
 Keywords:  reporter-feedback needs-testing  |     Focuses:  administration
---------------------------------------------+-----------------------------

Comment (by aenea):

 Replying to [comment:18 kanlukasz]:
 > Hello,
 >
 > Will there be any filter added to disable these log dumps?
 >
 > e.g. here:
 >
 https://github.com/WordPress/WordPress/blob/8d059b9fe25d2415c164b2f53e1a458ccdc20f99
 /wp-admin/includes/class-wp-automatic-updater.php#L672
 >
 >
 > Logs like these create unnecessary garbage and nothing more:
 >
 > {{{
 > [29-Jul-2024 22:23:07 UTC] Automatic updates starting...
 > [29-Jul-2024 22:23:08 UTC] Automatic updates complete.
 > [30-Jul-2024 10:22:56 UTC] Automatic updates starting...
 > [30-Jul-2024 10:22:56 UTC] Automatic updates complete.
 > [30-Jul-2024 22:23:37 UTC] Automatic updates starting...
 > [30-Jul-2024 22:23:38 UTC] Automatic updates complete.
 > [31-Jul-2024 10:23:31 UTC] Automatic updates starting...
 > [31-Jul-2024 10:23:32 UTC] Automatic updates complete.
 > [31-Jul-2024 22:23:14 UTC] Automatic updates starting...
 > [31-Jul-2024 22:23:15 UTC] Automatic updates complete.
 > [01-Aug-2024 10:22:44 UTC] Automatic updates starting...
 > [01-Aug-2024 10:22:44 UTC] Automatic updates complete.
 > }}}
 >
 > Many developers use `.log` to monitor some issues, using it with cron
 jobs, send logs elsewhere if something happen, etc., even in production
 (of course, we lock this file for public access).
 >
 > We are looking for important things there, not trivial repetitive
 information.
 >
 > Currently, one of my ideas is to use the `sed -i` command and run it
 with cron to cut those lines, but it's not a very convenient way to do it.

 I'd like to add my support to this comment. Having this unnecessary
 garbage in the log file is a nuisance. Why can't these messages be turned
 off?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61391#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform