Problem: I would like to add a filter to my custom search View that has options with different price ranges. For example, Less than 50, 50 - 100, and 100+.
Solution: There is not an easy way to accomplish this in Toolset using a standard price filter. You would have to create a separate custom field that holds a value that represents each price range, then filter based on that custom field. To automate the process, you could use a hook like save_post or pmxi_saved_post to check the current price and update the value automatically:
Problem: I would like to programmatically assign a Content Template to imported posts.
Solution: Content Template assignment is defined by a hidden custom field "_views_template" that holds the ID of the Content Template to apply to a given post. You can use the save_post hook to apply this value automatically whenever a post is saved:
function save_book_meta( $post_id, $post, $update ) {
$post_type = get_post_type($post_id);
// If this isn't a 'book' post, don't update it.
if ( "book" != $post_type ) return;
// - Update the post's metadata.
update_post_meta( $post_id, '_views_template', 12345 );
}
add_action( 'save_post', 'save_book_meta', 10, 3 );
Problem: I would like to show a View of taxonomy terms that are child terms of a specific parent term
Solution:
Here's how you can set this up:
1. Create a View of the taxonomy and add a Query Filter, filtered by term parent, where term parent is "None". This View will show the top-level terms in the term hierarchy. In the loop of this View, insert the term title or term link.
2. Create another View of the same taxonomy, again filtered by term parent, but this time where the term parent is set by the parent taxonomy View. In the loop of this View, insert the term title or term link.
3. Return to the first View and in the Loop after the term title, insert View 2.
4. Place View 1 on a custom Page somewhere to test it out.
Problem:
It was proving impossible to install reference sites even though all the requirements appear to have been met.
Solution:
The installation failed because the required plugins are expected to be installed but not active, which was not clear in the UI, and which has been fixed in an update to the installer.
Problem:
When will CRED provide support for multipart forms?
Solution:
It is one of the most requested features for CRED. When work on Types 3.0 (and related updates for the other plugins) completes in April we will then be able to switch resources towards adding support for such popular features.
En Toolset erratas, documentamos problemas conocidos y sus soluciones. Ahorre tiempo consultando allí primero y viendo si el suyo es un problema conocido. Mantenemos la lista corta. Hacemos lo mejor que podemos para resolver todos los problemas conocidos con cada lanzamiento de los plugines de Toolset.
Política de soporte
Nuestro personal le ayudará a usar los plugines de Toolset correctamente, le proporcionará la información que necesite, le ayudará a resolver problemas y lo asesorará con respecto a las mejores prácticas.
Sírvase asegurarse de incluir solamente un tema en cada solicitud de soporte.
