Dimitris Kalliris

FYI: https://tommcfarlin.com/comment-images-for-wordpress/

Hey there,

you can use the !important directive as Aristeides mentioned above.
You can find an example of demo Kirki controls file in
https://gist.github.com/aristath/d778d2592a4a6ce8f640#file-kirki-demo-controls-php-L229-L262

Hope that helps,
Dimitris

Hey there,

well, this is depending on the actual implementation you’re using into your theme.
You should calculate all other values into a custom function and then use them accordingly. I really can tell much as it’s really depending of your implementation, any CSS frameworks you may use etc.

You can take a look in a implementation based on Zurb Foundation in these links

https://github.com/presscodes/maera-foundation/commit/fee0905fcc4526dcae94d9eb134ab21fd77cd285

https://github.com/presscodes/maera-foundation/commit/0d66cf635287b3a8c79cff127c97700a0e37e4ab

Hope that helps,
Dimitris

Hey there,

can you please be more descriptive with your workaround?

Please advise,
Dimitris

The ‘required’ argument just hides the control until the dependencies are being met.
In order to do so, you should remove the ‘output’ argument and use that logic and CSS in a custom function.

Of course, this can be a matter of debate, as a feature request. You can always use github’s issue tracker for proposals. ??

Cheers,
Dimitris

Hey there,

I don’t know if I get that right. You can use the ‘output’ argument as shown in https://kirki.org/#output in order to output the CSS of a control
or
use a simple texarea control and enqueue it’s content though a simple function like

function custom_css() {
		$css = get_theme_mod( 'css', '' );
		if ( ! empty( $css ) ) {
			wp_add_inline_style( 'maera', $css );
		}
	}

Hope that helps,
Dimitris

Hey there,

you can use a ‘required’ argument in select control as follows

$controls[] = array(
		'type'        => 'select',
		'setting'     => 'select_demo_2',
		'label'       => __( 'This is the label', 'kirki' ),
		'description' => __( 'This is the control description', 'kirki' ),
		'help'        => __( 'This is some extra help. You can use this to add some additional instructions for users. The main description should go in the "description" of the field, this is only to be used for help tips.', 'kirki' ),
		'section'     => 'select_section',
		'default'     => 'option-1',
		'priority'    => 10,
		'choices'     => array(
			'option-1' => __( 'Option 1', 'kirki' ),
			'option-2' => __( 'Option 2', 'kirki' ),
			'option-3' => __( 'Option 3', 'kirki' ),
			'option-4' => __( 'Option 4', 'kirki' ),
		),
		'required' => array(
			array(
				'setting' => 'checkbox_demo',
				'operator' => '==',
				'value' => 1
			)
		)
	);

Hope that helps,
Dimitris

Same issue here. Just erased that and looking for a equivalent by the time I switched my client’s site into a multisite.

Can’t be enabled neither globally or in primary site.
Can’t be erased from plugins list.

Same issue here. Just erased that and looking for a equivalent by the time I switch my client’s site into a multisite.

Can’t be enabled neither globally or in primary site.
Can’t be erased from plugins list.

Hello,

If I am not mistaken, the textarea control is escaped for security reasons. I would suggest re-writing your method so that the end-user only has to enter a few parameters.

Here are examples of how I did it with Analytics:

https://github.com/briancwelch/maera-seo/blob/master/includes/class-Maera_SEO_Customizer.php#L80-L89

https://github.com/briancwelch/maera-seo/blob/master/includes/class-Maera_SEO.php#L128-L146

https://github.com/aristath/kirki/issues/69#issuecomment-77751998

Hey there,

this is more of a feature request and I find that pretty useful. Could you create an issue in github?
https://github.com/aristath/kirki/issues

Cheers,
Dimitris

Please consider reading
this article of @aristath.

Have a good one,
Dimitris

Hey there,

sorry to bother, is there any update?

Cheers,
Dimitris

Hey there,

I’m using a premium theme which overrides the woocommerce/templates/myaccount/form-login.php template file but all action hooks are in place. There’re just some markup & styling additions.

Maybe the do_action( 'woocommerce_login_form' ); is what we need?

In the Registration form the Captcha are actually there and working as should be.

Please advise,
Dimitris

Hey there,

you may didn’t notice the specs mention that

Requires: 3.5 or higher
Compatible up to: 3.5.2

I think that’s valid, isn’t it?

Cheers,
Dimitris