Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#43064 closed defect (bug) (maybelater)

wordpress on different port doesn't run customizer

Reported by: tpaksu's profile tpaksu Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Customize Keywords:
Focuses: ui, template Cc:



When using BrowserSync to develop themes on a different port like 3000, the customizer control pane does show but the preview iframe contents are not loaded and Chrome devtools shows this message:

Refused to display '' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors".

Is this related to the browser's iframe policies or can it be fixed within WordPress?

Change History (4)

#1 @tpaksu
6 years ago

  • Keywords dev-feedback added

I came up with a solution that doesn't modify the wordpress core itself.

This issue may be closed because wordpress might not find out whether it is running via browsersync or directly from the browser itself. I couldn't find a way so solved it with editing the browsersync configuration to pass a parameter to the PHP server.

#2 @westonruter
6 years ago

Is the home/site_url option set to

#3 @tpaksu
6 years ago

  • Resolution set to maybelater
  • Status changed from new to closed

Hi Weston,

I'm only using it for browsersync to automating CSS/JS development, I'm not always using port 3000 as the site_url. No problem. I don't need that anymore.

#4 @ocean90
6 years ago

  • Keywords dev-feedback removed
  • Milestone Awaiting Review deleted
  • Version 4.9.1 deleted
Note: See TracTickets for help on using tickets.