WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #28227, comment 7


Ignore:
Timestamp:
10/08/2016 03:53:10 PM (4 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28227, comment 7

    initial v1  
    1 This is largely implemented now in #30937. Now when there is an error when loading the preview you'll see the error message that the server outputs (assuming you have `WP_DEBUG` enabled).  One exception is when doing a refresh, any such error will not be shown since the refreshed iframe won't be displayed. If there is going to be a notification of an actual error even without `WP_DEBUG` then this will depend in part on having a notification area (#35210). Technically how the customizer will know there is an error when loading the page is that it will never receive a `ready` message, and thus it will know that there was a problem loading the window. This could be due to a server error or a network error.
     1This is largely implemented now in #30937. Now when there is an error when loading the preview you'll see the error message that the server outputs (assuming you have `WP_DEBUG` enabled).  One exception is when doing a refresh, any such error will not be shown since the refreshed iframe won't be displayed. If there is going to be a notification of an actual error even without `WP_DEBUG` then this will depend in part on having a notification area (#35210). Technically how the customizer will know there is an error when loading the page is that it will never receive a `ready` message, and thus it will know that there was a problem loading the window. This could be due to a server PHP error, or a network error, or a JS error.