Title: Fixing the Customizer
Last modified: August 20, 2016

---

# Fixing the Customizer

 *  [Erick Hitter](https://wordpress.org/support/users/ethitter/)
 * (@ethitter)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/fixing-the-customizer/)
 * Rewriting the site URL when invoking the customizer triggers the following error
   in the browser console:
 * > XMLHttpRequest cannot load [MAPPED DOMAIN]. Cannot make any requests from null.
 * Detecting the Customizer-spawned request and skipping `siteurl` rewriting is 
   pretty easy, and in my production environment, fixes the problem. My patch is
   available at [https://gist.github.com/4430520](https://gist.github.com/4430520).
 * [http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/](http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/)

Viewing 8 replies - 1 through 8 (of 8 total)

 *  [etfb](https://wordpress.org/support/users/etfb/)
 * (@etfb)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321151)
 * That looks promising. I’m having a similar problem with the Cart66 plugin, which
   works on one site and not another. The difference between the sites is that the
   first is using its default domain and the second has a different primary domain.
   The obvious conclusion is that Domain Mapper does something to make Cart66’s 
   AJAX functionality fail due to the domain being identified inconsistently.
 * I will use your technique to see if I can fix this. If I can, it would appear
   that this plugin will need some kind of whitelisting feature to enable other 
   plugins and features to work with it. I’ll report back with my results shortly.
 *  [etfb](https://wordpress.org/support/users/etfb/)
 * (@etfb)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321152)
 * Confirming that the patch definitely fixes the long-standing bug in this plugin
   relating to the use of the Customizer with domains outside the default. Needs
   to be rolled in ASAP.
 * Now hunting down the appropriate settings for the Cart66 incompatibility.
 *  Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * (@wpmuguru)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321153)
 * Get the development version.
 *  [Unsal Korkmaz](https://wordpress.org/support/users/unsalkorkmaz/)
 * (@unsalkorkmaz)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321183)
 * development version is not fixing problem atm.
    +1 for fix. thank you its working
 *  Thread Starter [Erick Hitter](https://wordpress.org/support/users/ethitter/)
 * (@ethitter)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321236)
 * I’ve updated the patch at [https://gist.github.com/4430520](https://gist.github.com/4430520)
   to detect the Customizer in a less-hacky way.
 * Any chance of getting this into the plugin sometime soon?
 *  Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * (@wpmuguru)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321237)
 * [@erick](https://wordpress.org/support/users/erick/) – see if Donncha has a minute
   to look at it.
 *  [David Gwyer](https://wordpress.org/support/users/dgwyer/)
 * (@dgwyer)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321238)
 * Having the same issues with the customizer not working. Is there an ETA on a 
   Plugin update anytime soon? 🙂
 *  Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * (@wpmuguru)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321239)
 * [@david](https://wordpress.org/support/users/david/) Gwyer – you can apply the
   patch provided in the original post. I probably will not be doing anything with
   the plugin for a while due to health reasons.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Fixing the Customizer’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-mu-domain-mapping.svg)
 * [WordPress MU Domain Mapping](https://wordpress.org/plugins/wordpress-mu-domain-mapping/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-mu-domain-mapping/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/reviews/)

 * 8 replies
 * 5 participants
 * Last reply from: [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * Last activity: [13 years, 1 month ago](https://wordpress.org/support/topic/fixing-the-customizer/#post-3321239)
 * Status: not resolved