WordPress 4.5.2 Image Upload Control Bug

  • I’m a web developer and currently working on a certain WordPress project. I’m using WordPress 4.5.2. The problem I find with this version is that no matter what fixes or libraries or plugins I employ, WordPress won’t work with the Image upload control in the Customizer. I’ve tried implementing the Image upload control using standard WordPress procedures as the codex suggests but all in vain. I’ve tried using the popular Kirki toolkit for the same but still to no avail. After a long search, I came across the Customizer library and have tried a number of times to make it work but still to no avail. I’ve tried using the WP-Customize-Image-Reloaded php script but still to no avail too. Simply put, WordPress 4.5.2 has one hell of a monstrous bug that breaks the Customizer each time an Image upload control is added in the code. The Customizer will either display nothing in the left pane or will display nothing in the left pane and then display gibberish text and input fields in the preview window bottom. The attached image can give you an idea of how it looks like. I’ve tried testing other controls like the textarea, color pickers, the media uploader, and some others and they work except for the Image upload control. I’ve come to the conclusion that the problem is infact inside WordPress itself. I’ve even tried fixing the issue using the contextarg as specified in the codex and even read tutorials to rule out possibilities of me being ignorant about the way things work; But still the Image upload control breaks the customizer as long as it’s there in the code. The problems persists no matter what. Now I’m here asking for your help people to make this work. May someone look into this. There’s no way I can be glad to use the customizer if it simply won’t coorperate with me no matter what I do.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter semwangajoshua

    (@semwangajoshua)

    Unfortunately it’s not possible because I’m working on localhost and the bug shows in the backend i.e., in the Customizer. I wish I could add an image to this post. And I’ve noticed similar behavior with the Twenty Sixteen theme. Twenty Fifteen and Twenty Fourteen is ok. I only have Piklist, Themecheck plugins active. So I don’t think they should be the cause of the problem. May be someone try creating a control using the Image upload control in the customizer and see what happens.

    1) does the image actually upload?
    2) if it uploads and you press ‘save’ in the customizer, does the image show in the front end?

    My test with twenty-fifteen shows the image in the customizer, but in twenty-sixteen it does not. That leads me to beleive there is a bug in how twenty-sixteen is processing the image, not a WP bug

    I just tested in Safari, FireFox and Chrome. It works fine in FireFox and Chrome but not in Safari.

    Have you tried a different browser? This could be a but in Safari….

    @semwangajoshua– Try using the beta version of Piklist. It might help. You can download it here >

    Thread Starter semwangajoshua

    (@semwangajoshua)

    Thanks for the reply Steve. I’ve actually been doing more investigation into the bug and have come to a conclusion that Piklist is the cause of the bug. Everytime I activated it, the bug showed up. And once I deactivated it, it disappeared the everything else runs smoothly. The bug is caused by an Image Upload Control. Once it’s part of the code, and Piklist is active, it shows up. I’ve already posted in the Piklist forum about the issue. Thank you guys for the help and concern. Let me wait to see what the Piklist support team comes up with about the issue.

    I’m on the Piklist support team ??

    Try the beta version.

    Thread Starter semwangajoshua

    (@semwangajoshua)

    Thanks for the reply and follow up Steve.I actually tried the beta version before the above response. I’m sorry I forgot to notify you about that. When I use the beta version, the gibberish/malformed input fields disappear and the Customizer remains blank. The only thing it will show is the name of the theme you’re currently customizing as usual. Other than that, nothing else. You can see the image of the Customizer as it looks after the upgrade to the latest beta version of Piklist on the Piklist forum on the post about the issue since I posted there. The ticket ID on the Piklist forum is: #6675 under the title: Image Upload Control Bug with WP 4.5.2 Customizer API

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WordPress 4.5.2 Image Upload Control Bug’ is closed to new replies.