Using Toolset's Import/Export, The only tabs on the new site's Import/Export are Types, Associations, and Forms. I don't see any options of Views.
Solution:
The export/import tab for Toolset Blocks has been disabled on purpose, our developers are working on it, but I am not sure when will this feature will be implemented.
Currently, you will try as you mentioned above, manually recreate the content template and view blocks.
I have a view that lists businesses and another view that displays a single business' details. Ideally, I would click on a "Details" link and pass a parameter to a popup, and the popup contains a view controlled by the parameter, but that doesn't work.
Solution:
1) Toolset Views does accept URL parameter to filter the view's result, it is a built-in feature of Toolset Views/Blocks plugin.
2) The problem is the Divi popup does not accept URL parameter
Problem:
The user collects payment for user registration, he would like to automatically create a post from a custom post type when the user completes the payment. And he would like to pass some data(custom fields) in the user registration form.
Solution:
This requires:
Post custom fields.
User custom fields, similar to the post fields needed.
CRED commerce form for users registration.
Custom code to create the post automatically when the order completes.
The cred_commerce_after_order_completed hook passes a $data object to the hooked function. The order_id is the "transaction_id" in the $data object. The created user is saved in a custom field of the order, called "_cred_post_id". Then we can pull the user fields from the user, create the custom post, and save the custom field values for the post.
Check this sample code:
add_action( 'cred_commerce_after_order_completed', 'my_cred_commerce_after_order_completed', 10, 1 );
function my_cred_commerce_after_order_completed( $data ) {
// get the order id
$order_id = $data['transaction_id'];
// get the user id
$user_id = get_post_meta( $order_id, '_cred_post_id', true);
// get user data to have a title for the post.
$user = get_userdata( $user_id );
// prepare post object
$post = array(
'post_type' => 'user-profile', // <== CPT slug
'post_title' => $user->user_login, // <== post title
'post_status' => 'publish',
'post_author' => $user_id, // <== Author
);
// Insert the post into the database
$post_id = wp_insert_post( $post );
// get user field
$phone = get_user_meta( $user_id, 'wpcf-phone-number', true );
$agency = get_user_meta( $user_id, 'wpcf-agency1', true );
$speciality = get_user_meta( $user_id, 'wpcf-specialty', true );
// create post field
update_post_meta( $post_id, 'wpcf-agency1', $agency );
update_post_meta( $post_id, 'wpcf-phone-number', $phone );
update_post_meta( $post_id, 'wpcf-speciality', $speciality );
}
Client wants a custom search View to be able to specify start and end dates as a between filter so that if there is any overlap between the range of start-date to end-date of the posts and the filtered date range then posts should match and be displayed.
Solution:
You need to compare the end date of your filter with the start date of your post and the start date of your filter with the end date of the post.
So a partial overlap of the posts and the filters being applied would be achieved if
- the post end date is later than the filter start date (the post hasn't already finished when our filter period starts), and
- the post start date is earlier than the filter end date (the post doesn't begin after our filter period is over)
Insert the start and end filters as normal, then edit them to swap over the URL parameters that provide the filter value.
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.
