- Timestamp:
- 05/23/2016 06:53:05 PM (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/wp-includes/customize/class-wp-customize-nav-menu-setting.php
r37518 r37539 75 75 * Previous (placeholder) term ID used before creating a new menu. 76 76 * 77 * This value will be exported to JS via the customize_save_responsefilter77 * This value will be exported to JS via the {@see 'customize_save_response'} filter 78 78 * so that JavaScript can update the settings to refer to the newly-assigned 79 79 * term ID. This value is always negative to indicate it does not refer to … … 101 101 * Status for calling the update method, used in customize_save_response filter. 102 102 * 103 * When status is inserted, the placeholder term ID is stored in $previous_term_id. 104 * When status is error, the error is stored in $update_error. 103 * See {@see 'customize_save_response'}. 104 * 105 * When status is inserted, the placeholder term ID is stored in `$previous_term_id`. 106 * When status is error, the error is stored in `$update_error`. 105 107 * 106 108 * @since 4.3.0 … … 448 450 * Storage for data to be sent back to client in customize_save_response filter. 449 451 * 452 * See {@see 'customize_save_response'}. 453 * 450 454 * @access protected 451 455 * @since 4.3.0 … … 460 464 * 461 465 * Any created menus will have their assigned term IDs exported to the client 462 * via the customize_save_responsefilter. Likewise, any errors will be exported466 * via the {@see 'customize_save_response'} filter. Likewise, any errors will be exported 463 467 * to the client via the customize_save_response() filter. 464 468 *
Note: See TracChangeset
for help on using the changeset viewer.