WordPress.org

Make WordPress Core

Opened 6 months ago

Closed 4 months ago

Last modified 3 months ago

#43064 closed defect (bug) (maybelater)

wordpress on different port doesn't run customizer

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

Description

Hi,

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 'http://wordpress.dev:3000/?customize_changeset_uuid=54b01da5-8dc3-4ff9-a3a2-3973cc2cbd22&customize_theme=rettica&customize_messenger_channel=preview-0' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors http://wordpress.dev".

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

Change History (4)

#1 @tpaksu
6 months ago

  • Keywords dev-feedback added

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

https://wordpress.stackexchange.com/questions/274049/wp-customizer-gulp-browsersync-refused-to-display-in-iframe

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
4 months ago

Is the home/site_url option set to http://wordpress.dev:3000?

#3 @tpaksu
4 months 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
3 months ago

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