With this hook, it has the product_id and based on the product ID, you can get the value of your custom field and it also offers the psot_id. So, what if you try to use the hook and based on the product_id get the value of your desired custom field and then assign it to your post based on the post_id.
Problem:
The forms' notifications are not sent even if the test email is sent and other WordPress emails are sent.
Solution:
Toolset puts the notifications emails into a queue, then sends it at the end of the page request process. Maybe, we can fix the issue with this form by disabling the queue. Add the following line to your wp-config.php file:
I have an odd thing happening with one of my views that should get posts that are published between two publish dates. The dates are set by a shortcode attribute and a custom date field set by the current page (post). It works fine for any set of dates EXCEPT if the date range crosses over from one month to the next month.
Solution:
It is a limitation of WP_Query, when the report-start "day" value is larger than the report-end "day" value, it will conduct the problem you mentioned above.
In your case, I suggest you setup the View filter with wpv_filter_query filter hook, for example:
Problem: I would like to set the value of a custom field automatically whenever a WooCommerce Order is created from the front-end of the site.
Solution: Use a custom code snippet with the save_post hook to programmatically set the custom field value:
function tssupp_set_select_value_1 ( $post_id, $post, $update ) {
$field_slug = 'custom-field-slug';
$forced_value = '1';
$post_type_slug = 'shop_order';
// you should not edit anything below this line
// - bail on wrong post type or on update
$post_type = get_post_type( $post_id );
if ( $post_type !== $post_type_slug || $update ) {
return;
}
update_post_meta( $post_id, 'wpcf-' . $field_slug, $forced_value );
}
// 1688213: Automatically select custom field value when order is created
add_action( 'save_post', 'tssupp_set_select_value_1', 100, 3);
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
