I wanted to add category (taxonomy) filters to a WordPress Archive built with the block editor; I could add a search, but wasn’t sure if taxonomy filters were possible in Toolset Blocks.
Solution:
In the Archive editor (Toolset → WordPress Archives), select the Archive block, click “Add Search Field,” choose “Post Taxonomy,” pick the taxonomy (e.g., Categories), select the input type (checkboxes/select/radio), and configure options and AJAX update in Custom Search settings.
Problem:
The customer wants to restrict access to posts with the term "Market News" so that only logged-in users belonging to specific Post Groups can view them.
Solution:
Toolset Access does not restrict access based on taxonomy terms assigned to posts. Instead, it uses Post Groups to manage access, where posts are manually assigned to Post Groups in the WordPress admin area, and access is controlled for entire user roles or individual users.
To achieve the desired functionality, you can consider using Toolset's conditional HTML to restrict content based on taxonomy. Here are some resources and suggestions:
While Toolset does not provide a built-in way to filter by taxonomy terms directly, combining the above methods with some custom code can achieve the desired result. However, support for custom code is beyond the scope of this forum. If custom implementation becomes a roadblock, consider seeking assistance from Toolset Contractors: https://toolset.com/contractors/
Problem:
Trying to change the user role from pending to approved provoked a fatal error on the site. Solution:
I changed the code and switched how the user role is added. I initiate a variable with the user's ID, remove the old role and add the new one as follow:
add_action('cred_submit_complete', 'cred_update_user_role_pending', 10,2);
function cred_update_user_role_pending($post_id, $form_data) {
require_once(ABSPATH.'wp-admin/includes/user.php');
if ( isset($form_data) && !empty($form_data) && isset($form_data['id']) && $form_data['id'] == 4981 ) {
// update the user role
$user = new WP_User( $post_id );
$user->remove_role( 'pending_vendor' );
$user->add_role( 'vendor' );
}
}
I also put in a check to make sure by the time the form is submitted, there's a valid formdata, it was causing a fatal error for some reason.
Problem:
Using cred form to remove user was triggering a fatal error and not deleting the user Solution:
I added a priority and fixed param numbers to the add_action call. I also test if the form_data is valid before moving forward to the deletion:
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.
