Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #39103, comment 1


Ignore:
Timestamp:
12/06/2016 06:35:34 AM (7 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39103, comment 1

    initial v1  
    33This was accounted for in widgets in the `\WP_Customize_Widgets::customize_register()` be checking to see if the `customize_save` ajax request is being made.
    44
    5 But, this is short sighted nevertheless. It will fail to work when implementing the changesets REST API endpoint. There should be a way to initialize `WP_Customize_Manager` without calling `preview` on all of the settings.
     5But, this is short sighted nevertheless. It will fail to work when implementing the changesets REST API endpoint (#38900). There should be a way to initialize `WP_Customize_Manager` without calling `preview` on all of the settings.
    66
    7 Aside: We'll need to refactor these to not use the `customize_save` Admin ajax as the signal but rather to check if `doing_action( 'publish_customize_changeset' )`
     7~~Aside: We'll need to refactor these to not use the `customize_save` Admin ajax as the signal but rather to check if `doing_action( 'publish_customize_changeset' )`~~