Opened 10 years ago
Closed 7 years ago
#31582 closed defect (bug) (fixed)
Catching PHP Fatal Errors on WordPress Theme Customizer
Reported by: | nightcoder | Owned by: | westonruter |
---|---|---|---|
Milestone: | 4.9 | Priority: | normal |
Severity: | normal | Version: | 4.1.1 |
Component: | Customize | Keywords: | needs-patch |
Focuses: | Cc: |
Description (last modified by )
I am developing a WordPress theme and added my a couple of new settings to the theme customizer panel. I don't have any custom JS code to share with you because i only added some new fields like shown at (http://codex.wordpress.org/Theme_Customization_API)
The Problem
I am getting this issue when i click the save and publish
button of the customizer panel
and the error comes with an ajax response. WordPress customizer
keeps working and refreshes the right frame as if data saved successfully. When you see the right frame refreshed, you think it is safe to close the customizer window and loose the unsaved data. Many themes has expensive operations such as creating dynamic css outputs only for custumizer so the fatal error may not be effect any other admin or front end part.
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30439 bytes)
The Request
Wouldn't be nice WordPress customizer analyze the ajax response for PHP fatal errors and promt a message to the user about the process interrupted.
Depends on #35210, notification area.
Attachments (1)
Change History (13)
#4
@
9 years ago
We need a good place to show error messages in the Customizer. @melchoyce and @michaelarestad any ideas? Any error message facility can then be used not only for fatal errors on the server, but also we can use it for showing validation messages in #34893.
#5
@
9 years ago
@westonruter I see you're chatting about a design in #31582 — will reply over there.
This ticket was mentioned in Slack in #core-customize by westonruter. View the logs.
8 years ago
#9
@
8 years ago
- Milestone changed from 4.6 to Future Release
Punting since we still need a patch and #35210 is still pending.
+1
This is largely a duplicate of #29932, but that ticket is more for catchable errors, whereas this issue is for reporting fatal errors.