Theme Customize – Blank Page

I think the reason for that is that the customizer now runs inside of wp-admin. The customizer should work if the dashboard is running under the mapped domain.

When the dashboard runs under the unmapped domain then the browser security prevents the customizer scripts running under the mapped domain to access the unmapped wp-admin.

Thank you for your reply Ron, I really appreciate it.

Aren’t the customizer scripts and wp-admin both on the same domain when you enable “Redirect administration pages to site’s original domain”?

Previously the customizer would not work because it the wpadmin area was mapped and the customizer was unmapped so you had to set “Redirect administration pages to site’s original domain”.

Is it not the reverse? The customize loads the mapped domain even though “Redirect administration pages to site’s original domain” is set?

Aren’t the customizer scripts and wp-admin both on the same domain when you enable “Redirect administration pages to site’s original domain”?

Yes, the customizer runs under wp-admin BUT the preview frame runs on the front end of the site which would give you the cross domain issue I described above.

Thank you very much for that. Unfortunately running the backends on the mapped domains doesn’t seem to be an option as then we would need to login individually to each client’s site losing a lot of time over the course of a day.

Will have to accept a blank theme customizer page it seems unless you happen to know of a work around to make the preview pane use the wp-admin URL ??

i found a fix for this problem here: https://gist.github.com/ethitter/4430520

i just used an or, so it should be backward compatible, replace gist-fix line 19 with this:
if ( (isset( $_POST['customize'] ) && isset( $_POST['theme'] ) && $_POST['customize'] == 'on') || ( is_a( $wp_customize, 'WP_Customize_Manager' ) ) )

Rouven, works great!

Ron does it make sense to add this to your main code? I’m not familiar with how to formally suggest code like the above but I imagine many others are having this same problem as Rouven and I.

Thanks again to you both.

Hi there.

We are seeing the exact same issue with all of our domain mapped users.

I too would like to see this added to the main plugin code…

Is this possible? (if so, when?)

Thanks!

The long term plan for domain mapping is discussed here: https://make.www.ads-software.com/core/2013/10/06/potential-roadmap-for-multisite/

I’m recovering from a difficult year & surgery. Combined with the plans to incorporate DM into core I don’t have any plans on rolling out a new version in the near future.