I need to rename a post’s title on front-end submit using two related items: the parent from a 1-to-many relationship (@movie-delivery.parent) and a company selected via a related field (company-to-deliver), but I don’t know how to fetch both related post titles in my PHP hook.
Solution:
Use the cred_submit_complete hook (relationships are fully saved then): get the parent with toolset_get_related_post( $post_id, 'movie-delivery', 'parent' ) → get_the_title(); get the company either from the post reference field ID via get_post_meta( $post_id, 'wpcf-company-to-deliver', true ) or, for true many-to-many, from toolset_get_related_posts( $post_id, 'company-to-deliver', ['role_to_return'=>'parent','limit'=>1] ); then concatenate and update with wp_update_post().
I want to auto-fill a hidden Toolset form field (cast-position) with the value of the ?pos URL parameter + 1, so that each new character entry gets the next position in the list. Using cred_before_save_data prevented the form from saving.
Solution:
Keep the field hidden and not required, then use the cred_save_data hook (after validation) to update the meta field
Or alternatively, use front-end JS with the form’s JS editor to populate the hidden input:
I want to restrict access to the entire site except the login page, but Toolset Access only allows controlling specific parts of the site, not full-site access.
Solution:
Use a third-party plugin like Restricted Site Access (https://wordpress.org/plugins/restricted-site-access/) to block the entire site except the login page; then use Toolset Access alongside it to control internal access by user role. Compatibility between the two should be tested on your specific setup.
I want to add a front-end delete button for a post that has multiple relationships, and I need to understand the difference between “Trash the post” and “Delete the post,” as well as whether related relationships are also removed.
Solution:
“Trash the post” moves it to the WordPress Trash and allows recovery; “Delete the post” permanently removes it. In both cases, Toolset removes the relationships linked to the deleted post, but the related posts themselves are not deleted unless custom code using before_delete_post and toolset_get_related_posts() is implemented.
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.
