Make WordPress Core

Opened 5 years ago

Closed 3 years ago

#48757 closed defect (bug) (invalid)

White screen after confirmation of admin email address

Reported by: jonfr2100's profile jonfr2100 Owned by:
Milestone: Priority: normal
Severity: major Version: 5.3
Component: Login and Registration Keywords:
Focuses: Cc:

Description

I get a white screen if I press 'The email is correct' on the first page after I log in with WordPress 5.3. There are no error messages displayed and this error has now happened to me on two separate websites running WordPress 5.3. The only way to avoid this issue is to press "Remind me later". Login in again does not work and there is no email sent from the WordPress software to the registered email address on the admin account. The page that appears has no code and is completely blank.

Attachments (1)

WordPress bug version 5.3.png (16.0 KB) - added by jonfr2100 5 years ago.
WordPress white screen bug confirm admin email button - this is image file

Download all attachments as: .zip

Change History (10)

#1 @shaharia.azam
5 years ago

Hi @jonfr2100 ,
Welcome to trac and thanks for reporting this. I will try to replicate this issue in my local environment. Let's see if the error is only for you or for all.

Thanks.

#2 @jonfr2100
5 years ago

This has now happened on three websites that I run. All websites are a upgrade from earlier versions whatever version what was before version 5.3 of WordPress.

@jonfr2100
5 years ago

WordPress white screen bug confirm admin email button - this is image file

#3 @anant101289
5 years ago

  • Keywords reporter-feedback dev-feedback added
  • Resolution set to worksforme
  • Status changed from new to closed

Hello @jonfr2100,

this is new feature added in wordpress 5.3 latest version,by default it will display every 6 months admin email confirmation screen.

i have solution for that, you will use below filter,to hide that screen,i recently update from 5.2 to 5.3 but i have not any issue.

 add_filter( 'admin_email_check_interval', '__return_false' )

#4 @anant101289
5 years ago

  • Resolution worksforme deleted
  • Status changed from closed to reopened

#5 @jonfr2100
5 years ago

The set-up on my websites is a common type of set-up. Its CentOs with Cpanel (for now) with mysql 10.1.43-MariaDB and php-7.2.24 and Apache 2.4.41. That it works for one person might have everything to do with their local set-up rather than what I am currently using. The host I am using supports WordPress directly and this is a dedicated server. This has happened on three WordPress sits that I have and each of them is set-up at different point in time with different start version.

#6 @jonfr2100
5 years ago

This bug continues with Firefox 71.0 64bit.

#7 @johnbillion
5 years ago

  • Keywords dev-feedback removed

@jonfr2100 There may be a fatal error occurring on your site. Can you check your PHP error log to see if there's a fatal error please?

#8 @jonfr2100
5 years ago

This was found to happen because of a modsecurity rule that my hosting provider did enforce. Once it was disabled (the rule resulting in this issue) everything started to work as it was supposed to do. The main error message was this one in the log.

" ModSecurity: Access denied with code 402 (phase 2). Match of "pm logout lostpassword postpass register resetpass rp" against "ARGS:action" required. "

#9 @SergeyBiryukov
3 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from reopened to closed

Thanks for the follow-up!

Closing as this appears to be an issue with a particular environment and not with WordPress core.

Note: See TracTickets for help on using tickets.