Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Jasonheffner

    (@jasonheffner)

    I saw you have a fix in place already in trunk, however it doesn’t seem to work in 3.4.2. I updated the code from

    from

    // don’t redirect theme customizer (WP 3.4)
    if ( isset( $_POST[‘customize’] ) && isset( $_POST[‘theme’] ) && $_POST[‘customize’] == ‘on’ )
    return;

    to

    // don’t redirect theme customizer (WP 3.4)
    if ( isset( $_POST[‘customized’] ) && isset( $_POST[‘theme’] ) && $_POST[‘wp_customize’] == ‘on’ )
    return;

    based on the POST data.

    Plugin Author Ron Rennick

    (@wpmuguru)

    At what point does it fail?

    Thread Starter Jasonheffner

    (@jasonheffner)

    You get a 301/302 redirect error when the AJAX call tries to load the preview, and you will get a blank iframe. I found your patch in 0.5.4.3 trunk above. It just turns out the exception put in place had the wrong parameters for the POST data.

    Here is the changeset: https://plugins.trac.www.ads-software.com/changeset/543145

    WP Core has a similar problem with Theme Changer as well if FORCE_SSL_ADMIN is set to true. You get a 301/302 error when it tries to load the preview since it’s being redirected to non-SSL. I submitted a bug report there as well.

    Plugin Author Ron Rennick

    (@wpmuguru)

    Thanks ?? The variable name may have been changed and I didn’t catch it. AT the time I wrote the patch there was no d on the variable name.

    I’ll be a couple days before I have a change to update trunk.

    Thread Starter Jasonheffner

    (@jasonheffner)

    It seems they must have also changed the last customize with wp_customize as well.

    Here is the POST parameters that I see

    customize_messenger_channel
    customized
    nonce
    theme
    wp_customize

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Theme Customizer needs exception’ is closed to new replies.