Problems with theme customiser on mapped domain

Viewing 6 replies - 1 through 6 (of 6 total)
  • Jason LeMahieu (MadtownLems)

    (@madtownlems)

    11 years, 6 months ago

    This looks like a pretty reasonable fix to me – I wonder what the authors think.

    Jason LeMahieu (MadtownLems)

    (@madtownlems)

    11 years, 5 months ago

    Dang – this didn’t get incorporated into the latest release 🙁

    Thread Starter Anonymous User 7600456

    (@anonymized-7600456)

    11 years, 4 months ago

    Yeah, the fix in the link above still works, even on the latest release.

    However, I don’t like hacking plugins just to be able to use the built in WordPress customiser.

    I would really appreciate it if the author would take a look.

    Thanks in advance.

    MissAmiaSays

    (@missamiasays)

    11 years, 4 months ago

    I need to ask a question about this plug in but don’t see where to start a thread.
    I hate the fact that I am “high jacking”
    I just want to be sure, is this an alternative plug in to WP Super Cache, W3 Total Cache etc.?

    Plugin Author Ron Rennick

    (@wpmuguru)

    11 years, 4 months ago

    Domain mapping is being added to WP core over a number of releases. I’m not planning any new releases of DM.

    Alex Delgado

    (@alexdelgado)

    11 years, 4 months ago

    That’s awesome news, but this is still a bug that should be fixed.

    I found that simply changing:

    if ( isset( $_POST['customize'] ) && isset( $_POST['theme'] ) && $_POST['customize'] == 'on' )

    to:

    if ( isset( $_POST['wp_customize'] ) && isset( $_POST['theme'] ) && $_POST['wp_customize'] == 'on' )

    fixes the customizer issues.

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

The topic ‘Problems with theme customiser on mapped domain’ is closed to new replies.