[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:  trunk
 Severity:  critical           |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  administration
-------------------------------+-----------------------------
Changes (by hellofromTonya):

 * milestone:  6.6 => 6.7


Comment:

 The fatal error potential is pre-existing, i.e. not introduced in 6.6
 cycle. With 6.6 RC1 happening today, moving to 6.7.

 Was discussed in today's bug scrub.

 @costdev [https://wordpress.slack.com/archives/C02RQBWTW/p1719325064056529
 shared]:
 >The maintenance mode screen was the only thing that was caused by 6.6 to
 my knowledge. The report looks to be a timeout/cURL failure that produced
 a Fatal Error. This kills execution and would lead to a "stuck"
 maintenance screen any time maintenance mode is enabled when a Fatal Error
 occurs. In that respect, that's a pre-existing issue with maintenance
 mode/Core's Fatal Error handler.
 >
 >To clarify: The when of the report's maintenance mode is what was related
 to 6.6, which we've now delayed. If the Fatal Error were to occur during
 the delayed updates/any other use of maintenance mode already in Core, the
 "stuck" maintenance mode screen would still occur. That part wasn't
 introduced in 6.6.

 [https://wordpress.slack.com/archives/C02RQBWTW/p1719325268214759 Me]:
 >A fatal error is concerning, but is pre-existing. So as it wasn't
 introduced in 6.6 and a resolution won't land before RC1 today, thinking
 it's okay to punt to 6.7.

 [https://wordpress.slack.com/archives/C02RQBWTW/p1719325319518069 Colin]:
 >Yep that sounds right to me. We should explore maintenance mode, as well
 as the fatal error handler/`shutdown` event to see if there's something we
 can do there (such as delete `.maintenance` before `shutdown` completes).

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