Sanesh Acowebs

Hi,Thanks for using our checkout field editor plugin. We have checked your issue on our demo(https://wcfe-free.demo.acowebs.com/checkout/) but couldn’t reproduce the issue. Can you please confirm that you are using the latest version of our checkout field editor plugin, Woocommerce and WordPress. If not, please upgrade and check again. Please share your checkout page url if that issue still remains.

Hi, this option is only available on our pro version plugin.

As we haven’t heard back from you further, we assume that this issue has been resolved at your end and considering this ticket as closed. Please don’t hesitate to get back to us if you require any further assistance or clarifications from our end in the future. Thanks!

Thanks for your comments and we’re glad to know that you liked the free version of our plugin. We have a lot of users with different themes using our free and pro version of our plugin.

Regarding your comment -The class attributes or other HTML attributes may break the checkout page frontend- We use the same classes that are used by Woocommerce and added some additional classes with our own prefix (these classes are not associated with any styling). If the free version of our plugin works, then the pro version will also have no frontend issues. There may be chances like, your theme not supporting Woocommerce class styles like form-row-wide, form-row-first and form-row-last. Also there are some plugins that add their own checkout fields with priority values. In this case also you can drag and adjust fields from backend settings.

Regarding the comment -The fields cannot be conditionally required- We already mentioned that we don’t have an option to make a field conditionally required, we only have the option to show/hide fields conditionally. And we don’t think any other checkout field editor plugins have this conditionally required option.

Regarding the comment -It displayed an “Array” on the order summary page instead of each field separately. Same for the order email- We are saving extra fields options as a single meta data. But It will display as a separate field and its value under the corresponding sections on order summary and order emails. This may not make any issues. If you want to retrieve a single field value then it can be retrieved using the order number. Also we are hiding this extra field values from the custom fields section on the backend order detail page.

We still believe that our plugin will work fine on your website. If there is any issue, we are happy to assist you. We provide a 30 day money back guarantee if you are not satisfied with our products. You can contact our support team for any issues and clarifications. Can you please share the ticket number if you have contacted our support team previously.

If you want that specific hook, then use like this:

add_filter( 'woocommerce_billing_fields', 'custom_woocommerce_billing_fields', 20 );

function custom_woocommerce_billing_fields( $fields ) {
	$fields['custom_field'] = array(
		'label' => 'Scary Field',
		'type' => 'checkbox',
		'class'     => array('form-row-wide'),
		'priority' => 90,
		'options'     => array(),
	);

	return $fields;
}

Hi, you can follow both ways, but we followed this hook for woocommerce documentation ( https://docs.woocommerce.com/document/tutorial-customising-checkout-fields-using-actions-and-filters/#section-6 ) and altered with our plugin accordingly.

Hi, Can you please change your code as given below. You need to use the “woocommerce_checkout_fields” hook to work with our plugin. Also you must add an options empty array to work in the case of checkbox field type. Our Pro version of plugin has options to add checkbox field type and many other field types. You can try this if you interested.

add_filter( 'woocommerce_checkout_fields' , 'custom_override_checkout_fields' );

function custom_override_checkout_fields( $fields ) {
		$fields['billing']['custom_field'] = array(
			'type'      => 'checkbox',
			'label'     => __('Scary Field', 'woocommerce'),
			'class'     => array('form-row-wide'),
			'clear'     => true,
			'priority' => 90,
			'options'     => array(),
		);

     return $fields;
}

Hi, this option is only available on our pro version plugin.

As we haven’t heard back from you further, we assume that this issue has been resolved at your end and considering this ticket as closed. Please don’t hesitate to get back to us if you require any further assistance or clarifications from our end in the future. Thanks!

Hi, we couldn’t find anything plugin specific from the shared debug log content. This may be related to the PHP version using. Can you make a support ticket at acowebs. Hope you are using the latest versions of WordPress, Woocommerce and other plugins.

can you please enable WordPress debugging and share debug.log content.

As we haven’t heard back from you further, we assume that this issue has been resolved at your end and considering this ticket as closed. Please don’t hesitate to get back to us if you require any further assistance or clarifications from our end in the future. Thanks!

Hi, This may be due to conflict with other active plugins. Can you please deactivate plugins one by one and check. Or can you enable WordPress debugging and share debug.log content.

No, you can’t name a field without a section name as a prefix. It also supports fields coming from other plugins as core fields created with woocommerce standards. In that case a name without section prefix is allowed.

As we haven’t heard back from you further, we assume that this issue has been resolved at your end and considering this ticket as closed. Please don’t hesitate to get back to us if you require any further assistance or clarifications from our end in the future. Thanks!