fix to tempnam() function breaks maintenance mode?

[cloudware]

This is a follow-up to #32135. Ref. Comment 4

The fix to the above bug appears to use the time() function to generate a temporary name rather than keep the name "/.maintenance"...

This surely will prevent WordPress from actually reporting to the users that the site is under maintenance, as it will be looking for a .maintenance file?

In some situations (DB upgrades etc) on busy sites the user interaction could have the potential for database corruption if the user is not prevented from access with the 'Under maintenance' page.

Keith

[dd32]

wp_tempnam() isn't designed to create a specific file, it's used for creating a random temporary file, the filepath parameter you can pass is designed to be used as a namespace/seed for that created file.

Calling wp_tempnam("/.maintenance") doesn't achieve the intended effect, and WordPress itself never makes such a call. The .maintenance file is always created by concatenating ABSPATH and .maintenance.