Any ETA on when the customizer will support all features?

[kmob2]

Hello,

I donated exactly 1 year ago to make redux compatible with the customizer and to get early access and the advanced extension. Most of the features have been working ever since I got early access, except for 1 major one, the "required" field. Now a year later it's still and outstanding issue.

I get that this is a free project and I do really have the highest respect for you guys investing so much time into this. However considering you made a crowed funding for this, and a year later there have been almost no major improvements on the customizer side, it's a bit worrying.

Is there any ETA on when that feature will be implemented?

[dovy]

@kmob2 I hear you. I have been out for the last year honestly. Long story short I haven't had the time due to three family deaths over the past 6 months and a new job.

I have been working on it, and things are leveling out to where I can work on things again. I just have been spread too thin.

On the positive side, I just fixed the repeater field in the customizer. :P

[kmob2]

Hello Dovy,

Hope you are well. I am very sorry to hear about all the personal losses you have had. I can't imagine how hard this must have been for you. I do feel a bit strange bringing this up again after all you have been through and all the free work you have already offered. I hope this doesn't come across the wrong way.

Is there any update on the "required" field implementation? This was pretty much the only reason I supported the kickstarter project and now 15 months later it's still not implemented.

Currently I am using jquery to apply css "display:none" and "display:list-item" on the redux fields inside of the customizer to replicate this behavior. Unfortunately on first page load of customizer, all the redux fields that were set to "display:none", which are then made visible again when pressing the required field, do not have any redux styles applied to them, only when clicking into the newly visible field, then the style gets applied.

I can't seem to find a solution to this.

Here's my ugly jquery approach:

//Fetch Body Background Settings On Page Load
var body_bg_image=$('input:checked', '#my_theme-general_body_bg_image').val();

if(body_bg_image == "1") {
    //Hide Gradient Panels
    $('li[id="my_theme-general_body_bg_gradient"]').css('display', 'none' );
};

//Body Background Field on Change
$("#my_theme-general_body_bg_image").find('input').change(function(){

    if($(this).val() == "1") {
        //Hide Gradient Panels
        $('li[id="my_theme-general_body_bg_gradient"]').css('display', 'none' );
        $('li[id="my_theme-general_body_bg_color2"]').css('display', 'none' );
    }

    if($(this).val() == "2") {
        //Show Gradient Panels
        $('li[id="my_theme-general_body_bg_gradient"]').css('display', 'list-item' );
        $('li[id="my_theme-general_body_bg_color2"]').css('display', 'list-item' );
    }
});

Edit: Creating a css class with visibility:hidden; position:absolute and left:999em, and then adding/removing this class via jquery seems to work. However I am not sure about the performance once I include all my redux fields.

[dovy]

Gah, I need to get on it. Seriously life has been crazy. Wife pregnant again and it's hard to work on things as much as I used to. I can't do anything this month, but I'll try digging in next month. I know WHAT to do, it's just going to take a bit of work. :-/

[adrianlbs]

Best wishes mate! Sorry for your loss and congrats for having another baby!

Cheers!