The issue here is that the user wanted to add a status option to their frontend form so that the post can be saved as a draft or publish based on the user's choice.
Solution:
This is possible but you will need to do it using a select field. Create a generic select field like the one below on your form and set the statuses you want the user to choose from.
The user will then select the status they want to submit the post as.
From there we can use a Cred hook to hook into the save post and then set the status there.
add_action('cred_submit_complete', 'my_success_action',10,2);
function my_success_action($post_id, $form_data)
{
// if a specific form
if ($form_data['id']==346)
{
if (isset($_POST['order_stat']))
{
// add it to saved post meta
$my_post = array(
'ID' => $post_id,
'post_status' => $_POST['order_stat'],
);
wp_update_post($my_post);
}
}
}
Now you will replace the my_custom_field with the slug of the generic field that you made. Note it would be best if this was a select field where the value and the display name is also the same.
Problem:
A form to add repeatable field groups includes a selector to specify which post they belong to. How to pre-select that post?
Solution:
Repeatable field groups are implemented as child posts of the post to which the fields belong, and the normal workflow for adding child posts where the parent is predefined is described in the linked documentation.
In this case, the client was including the forms to add repeatable field groups directly in the output of a View, in which case the parent post could be specified by using the wpv-post-id shortcode to provide the default value for the selector.
This page is set to show a different layout for "guests" - showing the login screen.
it works only in english (the default language). when you switch to french or german, you can actually see the content of the page and the access control for the post group doesn't work anymore.
Solution:
I suggest you setup one same layout for all user role, in this layout display a visual editor cell, and use Access shortcode [types_access] to display different contents for different user role.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
