Changes between Version 17 and Version 19 of Ticket #30937
- Timestamp:
- 04/07/2015 11:39:18 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30937 – Description
v17 v19 21 21 * With each save in the Customizer resulting in a new transaction post being created, then there is Customizer revision history (see #31088, #31089) 22 22 * Accessing the Customizer preview for a transaction needs no special capabilities since the transaction is updated by an authorized user via single Ajax request. This means that Customizer previews (frontend URLs with the transaction UUID amended) can be shared for anonymous users to review. 23 * Customizer Theme Switch (#31303) could preview another theme and refresh the Customizer without losing settings, and thus no AYS dialog would be needed. 23 24 24 25 Something else that motivated my investigation into Customizer transactions is thinking about how the Customizer will relate to the '''JSON REST API'''. How can the REST API be improved with the Customizer? If the REST API provides a `transactions` endpoint for doing CRUD operations on Customizer settings, and if the REST API also has global recognition for a `customize_transaction_uuid` query parameter in all requests, then it becomes possible for the Customizer to be used to preview changes in applications that merely interact with the JSON REST API, as long as they include the transaction UUID in the requests. … … 27 28 28 29 Initial alpha Core patch for Customizer transactions can be seen at: https://github.com/xwp/wordpress-develop/pull/61 30 31 See Make Core blog post: https://make.wordpress.org/core/2015/01/26/customizer-transactions-proposal/ 29 32 30 33 Related: