Make WordPress Core

Opened 6 years ago

Closed 4 months ago

#47974 closed defect (bug) (duplicate)

Fatal error without explanation

Reported by: cristianciuberea's profile cristianciuberea Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.2.2
Component: General Keywords: close 2nd-opinion
Focuses: Cc:

Description

Hello,

Today, sudenly wp-admin return this error https://prnt.sc/p1sz3t

I discoverd is from digitalaccespass plugin. if i disable it, wp admin works ok.

Now, the strange thing is that dap dont work even if i disable all plugins/all themes

So it something related to this site.

What disturbs me and is not the first time is that i dont receive an email with the error.

The message says it was send an email to administrator, but i dont receive any email.

I also enabled debug but no info there .

How can i help you to make send emails with fatal error every time?

Also, is there anything i can do to find the error?

Thank you

Change History (4)

#1 @dkarfa
6 years ago

Hey @cristianciuberea

Welcome to WordPress Trac! Thanks for the ticket.

Please note that this Trac is used for enhancements and bug reporting for the WordPress core software, not for individual support questions.

Please try the support forums to get help with your site: https://wordpress.org/support/.

#2 @cristianciuberea
6 years ago

Hi @dkarfa ,

Sure, will open one there, but the main purpose is to raise awareness about the fact that in multiple cases i did not receive any email about the fata error that ocurr in the site.

So I would like that to be solved in the future if posible :)

Thank you

#3 @sabernhardt
13 months ago

  • Keywords close 2nd-opinion added

Trac has some related tickets.

  • #52560: Changeset [51076] should have stopped any mention of an email when it is not sent.
  • #53707: The message can be edited for a situation when sending the email succeeds but then it cannot be received.
  • #60619: A DNS section in Site Health could help with email deliverability.

Those are not exactly duplicates, but I do not know what other task might be done on this ticket.

#4 @karmatosed
4 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #60619.

Thank you for reporting this @cristianciuberea. I agree with @sabernhardt that as there are related tickets, the recommendation to close this one is something we should do, particularly after it has been with that status for a little while and nobody has raised anything to counter that. This doesn't mean we can't progress with anything on those tickets and or even reopen this one.

Thank you everyone. For now I am closing with the status of duplicate, picking the one that is still open. I am aware that might not fully fit the purpose so happy for someone to counter that status.

Note: See TracTickets for help on using tickets.