#51524 closed defect (bug) (fixed)
"There has been a critical error on your website" should be changed to "There has been a critical error on this website"
| Reported by: | techboyg5 | Owned by: | desrosj |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.6 |
| Component: | Site Health | Version: | |
| Severity: | normal | Keywords: | has-patch commit |
| Cc: | Focuses: | ui-copy |
Description
"There is a critical error in your website" is the current message when a PHP error occurs in WordPress.
But if the website is not your own, then this message does not make sense.
I think it should be changed to "There is a critical error in this website", which makes sense no matter who accesses the website.
Attachments (3)
Change History (15)
This ticket was mentioned in PR #600 on WordPress/wordpress-develop by techboyg5.
6 years ago
#1
- Keywords has-patch added
#4
@
6 years ago
- Focuses ui-copy added
- Keywords has-patch added
- Milestone Awaiting Review → 5.6
- Owner set to
- Status new → accepted
- Version 5.5.1
Hi,
Good point. I think we definitely need to address this issue.
I tested the patch and it looks good to me. Adding to milestone 5.6.
#5
@
6 years ago
- Keywords dev-feedback added
In 51524.diff, I replaced the sting only for visitor-facing errors.
Indeed we don't need to replace "your" when we are under Recovery mode or is_protected_endpoint() contexts.
#6
@
6 years ago
- Summary "There is a critical error in your website" should be changed to "There is a critical error in this website" → "There has been a critical error on your website" should be changed to "There has been a critical error on this website"
#7
@
6 years ago
I actually think it makes sense to use this for all three scenarios, even non-public pages, it may still not be your site, for example the user logging in may just be managing it for a client.
So with that I think pr600 makes sense to use.
#8
@
6 years ago
- Keywords dev-feedback removed
@audrasjb do you agree that we can move forward with PR600? If yes, can we mark this one commit?
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Trac ticket: https://core.trac.wordpress.org/ticket/51524