- This topic has 2 replies, 2 voices, and was last updated 5 years, 7 months ago by
.
-
Posts
-
-
I’m using WordPress 4.5.2. The problem I’ve found is that no matter what fixes or libraries or plugins I employ, the WordPress Customizer won’t work with the Image upload control. 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. Today, I decided to investigate if the plugins aren’t the cause of the bug that breaks the Customizer each time an Image upload control is added in the code. I’ve deactivated all the plugins and the Customizer worked fine. I then started activating the plugins one by one while running the checking th Customizer to see if one of them breaks it. To my dismay, Piklist was the one that was breaking the Customizer. When I activate Piklist,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. When I upgrade to Pikist 0.9.9.8, the Customizer goes blank without any controls. The attached image can give you an idea of how it looks like. All this happens as long as an Image upload control field is added in the code that is run by the Customizer. Whether it is added using standard procedure, or using a library like the Customizer library by Devin Price. Even when using the popular Kirki toolkit, the Customizer breaks if one of the controls is an Image upload control. Remove the Image upload control from the code, the Customizer runs. Put it back, it breaks. I’ve tried testing other controls like the textarea, color pickers, the media uploader, and some others and the Customizer works except for the Image upload control. I’ve come to the conclusion that the problem is infact inside Piklist because it’s the one that breaks the Customizer. 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 and Piklist is running/active. Now I’m here asking for your help people to make this work. The greater part of my project is run by Piklist. Redoing allover again what I’ve already accomplished with Piklist using another alternative to Piklist is my most dreaded nightmare. I love Piklist and I want to continue using it for it took me some time to decide about taking it up. Besides, it’s the best framework out there. Until then, I’m stuck and only counting on your help to move forward. -
@semwangajoshua– This is the first time we’ve heard of an issue with Piklist 0.9.9.8 and the customizer.
I suggest you deactivate some of your other plugins to see which one is conflicting. You may also want to try a WordPress default theme.
Let us know what you find.
-
I’d actually tested earlier while the plugins are deactivated. This time around, I’ve actually deleted all plugins and left Piklist only. The problem persists. I’ve tested the the Twenty Sixteen theme with Piklist deactivated and it works well. When I activate Piklist again, the Customizer breaks. That is what happens with the Twenty Sixteen theme. I’ve tested the Twenty Fifteen and Twenty Furteen themes in the same way; surprisingly the Customizer works well with them activated. Even with Piklist activated, they still work well unlike mine and Twenty Sixteen. So in short, My Custom theme and Twenty Sixteen won’t work with Piklist activated. Twenty Fifteen and Twenty Fourteen themes work with Piklist activated and even when deactivated. To honest with you Steve, as much I think Piklist has something to do with this bug, I very strongly smell a rat in WordPress 4.5.2 about the bug. I’ve done enough research about the issue and there quite a number of genuine posts that show that actually WordPress 4.5.2 may be highly contributing to the problem. This Treehouse tutorial here by Zac Gordon of Treehouse is basically talking about fixing a related issue with the Image Upload Control. Until then, I’ll wait on you guys. Thanks a lot for the support. I appreciate it very much
-
- You must be logged in to reply to this topic.