WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #31582


Ignore:
Timestamp:
03/10/2015 02:43:30 PM (5 years ago)
Author:
ocean90
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31582 – Description

    initial v1  
    1 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 (<a href="http://codex.wordpress.org/Theme_Customization_API" rel="nofollow">http://codex.wordpress.org/Theme_Customization_API</a>)
     1I 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)
    22
    3 <strong>The Problem</strong>
     3== The Problem
    44
    55I 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.
    66
    7 <blockquote>  <strong>Fatal error</strong>:  Allowed memory size of 67108864 bytes exhausted
    8   (tried to allocate 30439 bytes) in
    9 </blockquote>
    10 <strong>The Request</strong>
     7{{{
     8Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30439 bytes)
     9}}}
     10
     11== The Request
    1112
    1213Wouldn't be nice WordPress customizer analyze the ajax response for PHP fatal errors and promt a message to the user about the process interrupted.