I would like to use both radio buttons (desktop) and a dropdown (mobile) in the same View and toggle visibility with CSS, but the radio buttons do not work on desktop while the dropdown works on mobile.
Solution:
Having two filter controls for the same query in one View is not supported. Create two separate Views—one for radio buttons and one for the dropdown—to achieve this setup.
I created a Repeatable Field Group “Opening time” and tried to add filters in a View, but the expected options don’t appear—only a grey, locked filter shows, and I can’t select additional filters.
Solution:
Set the View’s Content selection to the RFG (“Repeatable Field Groups from the current Gym > Opening Hours”); the owner filter is added and locked by design. Create a separate View to list the RFG items and insert it into the Gym Single Content Template (or use nested Views in legacy mode if building on a separate page).
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:
