WordPress.org

Support

Support » Plugins and Hacks » WordPress MU Domain Mapping » [Plugin: WordPress MU Domain Mapping] Conflict with 3.4's Theme Customizer

[Plugin: WordPress MU Domain Mapping] Conflict with 3.4's Theme Customizer

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Ron Rennick

    @wpmuguru

    Try the development version http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/developers/.

    The theme customizer works for me with the development version but I haven’t had any feedback from anyone else to confirm. If it works fine for you can you let me know?

    Oh, thank the gods! Some pillock over in the #wordpress channel insisted that I must be making this up, but I’ve never once succeeded in getting the Customize feature to work and, sure enough, I use the Domain Mapping pluging — which I can’t switch off because it would disable all my sites! I’ll try the dev version and see if it’s fixed.

    … Aaaaaand: it still doesn’t work. Bugger. Well, at least I now know who to blame.

    Plugin Author Ron Rennick

    @wpmuguru

    @eftb – what is the version number of the version you have installed?

    Ron – latest version of everything: WordPress 3.4.1, plugin version 0.5.4.3. I have my WP installation on example.com, and several sites with their primary URLS on foo.com, bar.com and baz.com. Sites like a.example.com, b.example.com and c.example.com all work fine with the customizer, but any site like x.foo.com or y.bar.com does not.

    Clearly what’s happening is the Customizer is refusing to see, say, “afoo.example.com” (which is the default name for the site at a.foo.com) as a reasonable alias for a.foo.com, somehow. Somewhere in your code, an alias is being translated too early or too late.

    Contact me on bat@flurf.net and I’ll point a couple of different domains at your test site of choice so you can see the problem in action.

    Plugin Author Ron Rennick

    @wpmuguru

    Somewhere in your code, an alias is being translated too early or too late.

    No, that’s not the issue. I only had to add 2 lines of code to get the customizer to work with mapped domains. Did you edit the site url of the sites to get them to work as mapped domains?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Conflict with 3.4's Theme Customizer’ is closed to new replies.
Skip to toolbar