[wp-trac] [WordPress Trac] #31582: Catching PHP Fatal Errors on WordPress Theme Customizer

[WordPress Trac]

#31582: Catching PHP Fatal Errors on WordPress Theme Customizer
--------------------------+-----------------------------
 Reporter:  nightcoder    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Customize     |     Version:  4.1.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------
Description changed by westonruter:

Old description:

> 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.
>
> Thank you.

New description:

 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.

--

--
Ticket URL: <https://core.trac.wordpress.org/ticket/31582#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform