Support » Plugin: WordPress MU Domain Mapping » Fixing the Customizer

Viewing 8 replies - 1 through 8 (of 8 total)
  • 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.

    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

    (@wpmuguru)

    Get the development version.

    development version is not fixing problem atm.
    +1 for fix. thank you its working

    I’ve updated the patch at 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

    (@wpmuguru)

    @erick – see if Donncha has a minute to look at it.

    Having the same issues with the customizer not working. Is there an ETA on a Plugin update anytime soon? 🙂

    Plugin Author Ron Rennick

    (@wpmuguru)

    @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.