Solution:
We will update Toolset to use Bootstrap 4, but that hasn't happened yet.
In the meantime if you are using a theme that loads Bootstrap 4 you can disable Toolset from loading Bootstrap 3 on the Toolset > Settings page. Experience suggests it mostly works fine, just a few tweaks here and there are required that you will need to be on the lookout for.
Problem:
When you add a Custom Field to a RFG, that Custom Field shows as not belonging to any group in Toolset > Custom Fields Control screen.
This is wrong, since the Field belongs to a RFG, and that RFG belongs to a CF group.
Problem:
Client is using Bootstrap accordions for a View output but cannot get them to work, and has the requirement that the first accordion should be open.
Problem:
The client is producing a list of content that he wants to appear in modals and has the problem that all of the links to open a modal open the same first modal content.
Solution:
The modals implementation requires linking to modal elements by their id, and the loop output section of the View uses "static" markup for the id, so the markup for each modal has the same id. You need to generate unique ids using the wpv-post-id shortcode (for posts) or wpv-taxonomy-id shortcode (for taxonomy terms), e.g.
Problem:
Client wants to use Toolset Form notifications as contact forms, without storing the submitted posts in the database.
Solution:
Forms will always publish a post. If you don't want those posts to be retained, you could
1. add post expiration and have the posts trashed within minutes of them being published. This won't delete them, you would need to use some kind of utility to routinely empty the trash; or
2. use the CRED API to run some code once the form had been submitted and then delete the post. The latest effective hook that could be used in this case would be the cred_notification_recipients hook.
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.
