0.5.1 breaks Customizer

  • After updating to version 0.5.1, the Customer is no more usable.

    By accessing it, the following error messages occur in the browser console:

    TypeError: undefined is not an object (evaluating 'wp.customize.section("static_front_page").container')
attr — jquery.min.js:2:65774

    Hint: We removed the section static_front_page in our theme:

    $wp_customize->remove_section( 'static_front_page' );

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey @kittmedia thanks for bringing this to my attention! Sorry this is causing you issues. As of v0.5.1 Disable Blog assumes that section is there and tries to update it, but in your case it’s not there so it throws this error.

    I’ll try to get some time on replicating and fixing this issue for the next release.

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Just a follow up to note that version 0.5.2 introduced a fix for this issue.

    I’m going to close this topic, but if you are still encountering issues please feel free to re-open or reach out with a new issue.

    Thread Starter Matthias Kittsteiner

    (@kittmedia)

    Unfortunately, it’s still broken because the check is wrong. You check for wp.customize.section("static_front_page") !== 'undefined', but the section is undefined and not a string 'undefined'. So either check for plain undefined or even better check its type: typeof wp.customize.section("static_front_page") !== 'undefined'. ??

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Oh man, what a silly thing for me to miss – not sure why the typeof didn’t get in there! ???♂?

    Thanks following up on this, super appreciate it.

    I’m offline for the rest of the week, but I’ll get that updated next week.

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey again! This should be fixed in v0.5.3. Please let me know if you have any further issues, I’ll leave this topic open just in case ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘0.5.1 breaks Customizer’ is closed to new replies.