Problem: I have a custom search View with two control fields. I would like to require the User to select a value in both fields before any results are shown. As it is now, when the page loads all the results are shown. I would like to show no results.
Solution: @e have an API that is helpful for this situation: wpv_filter_query_post_process. This will allow you to intercept the search results and test the query. If either option is blank, or 0, show no results.
// custom filter that shows no search results if either filter is empty
add_filter( 'wpv_filter_query_post_process', 'drop_empty_search_query_post_process', 10, 3 );
function drop_empty_search_query_post_process( $query, $view_settings, $view_id ) {
$ids = array(12345);
if (in_array($view_id, $ids)){
if (
// supplier type filter needs to check for not '0' as well as not empty
( isset($_GET['wpv-supplier-category']) && $_GET['wpv-supplier-category'] != '0' )
&&
// location filter needs to check for not '0' as well as not empty
( isset($_GET['wpv-area-served']) && $_GET['wpv-area-served'] != '0' )
) {
} else {
$query->posts = array();
$query->found_posts = 0;
$query->post_count = 0;
}
}
return $query;
}
Replace 12345 with the numeric ID of this View. You can customize the "No results found" message in the View's Loop Output editor panel.
Problem: I would like to delete a post when a User's WooCommerce Subscription is canceled or expires.
Solution: Toolset does not have any hooks that will help you respond to WooCommerce Subscription events, so I would ask WooCommerce Subscriptions' support team if they offer an API that will allow you to perform some action when a subscription is canceled or expires. If so, then you can use some custom code to set the post to "draft" status, which would effectively remove it from the front-end of the site. You could reinstate the post at any time if the subscription is renewed. Here's an example ticket on stackoverflow that modifies a post's status: https://wordpress.stackexchange.com/questions/12512/how-to-update-page-status-from-publish-to-draft-and-draft-to-publish
Problem: I have a new User CRED form that allows guests to register. When they submit the form, I would like to automatically create a custom post that includes information from the form, and I would like to restrict access to that post to the created member only.
Solution: 1. Create a Custom Post Entry for "Band Name" on Member Registration.
This can be accomplished with a bit of custom code using the cred_save_data API.
add_action('cred_save_data', 'my_save_data_action',10,2);
function my_save_data_action($post_id, $form_data)
{
if ($form_data['id']==1234)
{
$my_post = array(
'post_title' => $_POST['some_custom_input'],
'post_status' => 'publish',
'post_author' => $post_id,
'post_type' => 'band-post-type-slug'
);
// Insert the post into the database
wp_insert_post( $my_post );
}
}
1234 should be changed to match the numeric ID of your User CRED form, and 'some_custom_input' should be changed to match the name of an input containing the data you would like to use in the Band post title. The data in the $my_post array can be modified according to the wp_insert_post documentation.
2. Only allow the registered Member edit his own Band Page.
In the code I provided above, I have configured the new post's author to be automatically set to the User that was just created during registration. Once this registration form is up and running, you should be able to use Access post and form restrictions based on the post Author (Member can edit own vs Member can edit any).
Problem:
How to associate parent post ID when you create child posts using CRED form.
Solution:
You can add CRED generic hidden field to hold the parent ID of child post and build custom shortcode that return the desired parent id in this case.
Problem:
The problem being described in this ticket is that the customer would like to know if Types has the ability to query an external database.
Solution:
Though this is a good Idea, it is unfortunately not possible 🙁
This is because our plugins utilize wordpress native db query function in order to query the database. This function only queries the tables within the current database that the installation lives in. It is not able to perform cross database queries.
Any such functionality would require the use of custom coding as you currently tried.
This is something that is out of the capabilities of our Toolset plugins.
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
