Saravana Kumar K

Hi,

Can you show us the actual page, where the issue is happening.?

Hi,

One clarification.

$_fields["Your Field Label"] = get_post_meta($_order->get_id(), "_custom_{Your Custom Field's Key}", true);

Here have you updated the "_custom_{Your Custom Field's Key}" key with your actual custom field’s key.?

If yes and still facing issue, let me have a temp access, I will try to fix it.

Hi,

If you disable Fields Factory, does the issue solved.?
Also are you using Fields Factory custom pricing functionality.?

Anyway, I will test the plugin you mentioned, and will let you know the issue.
(I guess this is the one you using https://wordpress.org/plugins/exchange-rates-today/)

Its already i17n ready, the wc-field-factory is the text domain.
But as for as the custom fields concerns, it is stored as custom post meta, where the convention i17n is tricky to use.

SO I opted for custom approach for multi language support, you can see the details here.

If you feel I am missing something, or could have done differently, pls let me know.

Hi, will look into both items. pls wait for few days, as we are nearing for the next release which will have a stable build and more features.

• This reply was modified 4 years, 1 month ago by Saravana Kumar K.

Hi, pls add the following snippet on your theme’s functions.php file

function add_fields_on_order_email($_fields = array(), $_sent_to_admin, $_order) {	
	
	if ($_sent_to_admin) {
		$_fields["Your Field Label"] = get_post_meta($_order->get_id(), "_custom_{Your Custom Field's Key}", true);
	}
	return $_fields;

}
add_filter("woocommerce_email_order_meta_fields", "add_fields_on_order_email", 10, 3);

I am working on this, hopefully I will send you the pre build within three days.