Problem: A "Read More" link to the current post in a View loop, without showing the raw URL.
Solution: Add a Button block in the loop, set its text to "Read More," and set its URL to the dynamic post URL. Alternatively, put the original link code in an HTML block.
The website was making frequent Toolset requests to /wp-admin/admin-ajax.php, increasing resource usage even on pages without auto-advancing sliders.
Solution:
Review each View for AJAX pagination, automatic sliders, AJAX custom-search updates, front-end sorting, infinite scrolling, or map updates. To identify requests, use the browser’s Network panel, filter for admin-ajax, and inspect each request’s action parameter; Toolset actions use the wpv_ prefix.
A legacy nested View—where a parent View lists taxonomy terms and a child View lists posts assigned to each term—needed to be rebuilt using Toolset Blocks.
Solution:
Nested Views are not supported in the Block Editor, so any Views that require nesting must remain in Legacy mode.
The customer created a view with two query filters: (1) the page must be a subpage of the page on which the view resides, and (2) the custom field "Card Exclude" must not have the value "1." Despite having four subpages, with only one marked as excluded, the view displayed no pages. Additionally, the unchecked state of the checkbox field was not saving a value to the database.
Solution:
The issue stemmed from how checkbox field values were stored in the database. If the checkbox was never saved, it remained absent in the database. If checked and then unchecked, it stored a value of 0, while being checked saved a value of 1. The workaround applied involved manually saving the field as true (1) and then unchecking it to store false (0), allowing the query filter to function correctly. Additionally, two other solutions were suggested:
1- Using a conditional statement in the Loop Editor: [wpv-conditional if="( $(wpcf-exclude-card) ne '1' )"].
2- Custom code in the query to handle cases where the field might be NULL or 0.
Nous documentons les problèmes connus et leurs solutions dans Toolset erratas. Pour gagner du temps, vérifiez d’abord dans cette rubrique si le problème auquel vous êtes confronté est un problème connu. Cette liste est volontairement courte. À chaque publication d’extensions de Toolset, nous nous efforçons de résoudre tous les problèmes connus.
Politique d’assistance
Le personnel Toolset vous guidera volontiers pour utiliser correctement les extensions Toolset, vous fournir les informations dont vous avez besoin, vous aider à résoudre les problèmes et vous conseiller quant aux meilleures pratiques.
Merci de veiller à ce que chaque ticket d’incident ne référence qu’un seul incident.
