Make WordPress Core

Opened 10 years ago

Closed 14 months ago

Last modified 10 months ago

#38573 closed defect (bug) (maybelater)

Ajax requests in customizer controls don't inject customized state as done in preview

Reported by: westonruter Owned by:
Priority: normal Milestone:
Component: Customize Version:
Severity: normal Keywords: needs-patch
Cc: Focuses: javascript

Description

In the customizer preview, Ajax requests now get the customized state injected via jQuery.prefilter. In the customizer controls pane, however, this was not also implemented. This is important to ensure that that requests to the REST API will return back the expected previewed state.

Also relates closely to #38122.

Attachments (1)

38573.wip.diff (11.4 KB ) - added by westonruter 10 years ago.

Download all attachments as: .zip

Change History (8)

#1 @westonruter
10 years ago

  • Owner set to westonruter
  • Status newaccepted

#2 @westonruter
10 years ago

In 39138:

Customize: Ensure page/post stubs are included in listings and searches for available nav menu items.

Include the customized state in the Ajax requests to load items and search items.

See #38573.
Fixes #38122.

#3 @westonruter
10 years ago

  • Milestone 4.7Future Release
  • Owner westonruter removed
  • Status acceptedassigned

I don't think this is important to address right now. It will play an important role in #37887. Otherwise, any plugins that do REST API calls can just use POST with _method=GET as shown in requests to fetch available nav menu items.

#4 @westonruter
10 years ago

  • Use URL state for Ajax requests instead of wp.customize.settings. Move to base, but then can't use existing query params?
  • Eliminate add request previewing wrapper so that underlying function can be overridden?

#5 @celloexpressions
10 years ago

Taking off of the no-replies list.

#6 @westonruter
14 months ago

  • Resolutionmaybelater
  • Status assignedclosed

#7 @sabernhardt
10 months ago

  • Milestone Future Release
Note: See TracTickets for help on using tickets.