Hi Nick,
Thank you for waiting, while I deployed the forms with the discussed requirement on my test website.
I'm going to break down the steps in multiple logical parts so that they can be easier to follow:
1. First, we'll need a main container or a wrapper for these forms, which can hold them in the scope of a current "Provider"
( which is linked to the currently logged-in user )
You can create a post view and name it something like "View to show current provider's form".
In this view's settings, you'll select "Providers" in the content selection and include a post author "Query Filter" to show only those posts where the author is the same as the currently logged-in user.
( and this should always return only 1 "Providers" post )
Screenshot: hidden link
In that view's "Loop Wizard" you can select the "Unformatted" display layout and in the content template for this view's loop item, you can include heading for the first form "Select Speciality:".
2. Since the first step is to select a "Specialty", you can create a post form named "Form to edit a provider - select specialty".
In the form's settings, you can set it to edit existing "Providers" posts, and keep the original status of the form, while keep showing the form after the submission.
Screenshot: hidden link
In the fields section, you'll only need to include the "Specialties Providers" field, and you can set its label to something like "Select Specialty".
Screenshot: hidden link
3. Once this form is ready, you can place its shortcode in the view created in step 1, below the heading "Select Speciality:".
[cred_form form='form-to-edit-a-provider-select-specialty' post='[wpv-post-id]']
Note: how the current provider post's ID is passed in the post "attribute" to tell the form, which post to use for editing.
( ref: https://toolset.com/documentation/user-guides/front-end-forms/cred-shortcodes/#cred_form )
Screenshot: hidden link
As a result, the first form to select a specialty is ready.
When you'll insert this view from step 1 on a test page, you'll see a form with a list of specialties to choose from and a submit button.
Screenshot: hidden link
Once a provider will select a specialty from the list and submit the form, it will be connected with his/her provider post.
4. The next step would be to create a form to select a "subspecialty" but with only the options linked to the selected "specialty".
You'll create a new post form and can name it something like "Form to edit a provider - select subspecialty".
In this form's settings too, you'll set it to edit a "Providers" post, while keep showing the form and keep the same status for the post.
Screenshot: hidden link
Since only one "subspecialty" can be selected for a provider, you can include "Radio" type generic field in this form and make it a required field.
For the slug of this field, you can add "select-subspecialty" and for a source of options, you can set it to get options from a custom shortcode "[show_output_subspecialties_options]".
( explained in the next step )
Screenshot: hidden link
5. One great benefit of generic fields ( ref: https://toolset.com/documentation/user-guides/front-end-forms/inserting-generic-fields-into-forms/ ) is that we can dynamically populate their options, using views. The expected format for this is a valid JSON object, which can be easily achieved using views.
Example:
{"value": "value1", "label": "Label 1"}, {"value": "value2", "label": "Label 2"}....
You can create a new post view and name it something like "View to show Subspecialties options related to a Specialties".
In the content selection settings, you'll select "Subspecialties" post type and in the "Query Filter" section, you'll include a post-relationship filter to only get those posts which are related to a post whose ID is passed through a shortcode attribute "wpvrelatedto", in "Specialties Subspecialties" relationship.
Screenshot: hidden link
In the "Loop Wizard", you'll need to select "List with separators" option and you can structure the final content in the "Loop Editor" section like this:
[wpv-layout-start]
[wpv-items-found]
<!-- wpv-loop-start -->
<wpv-loop>
[wpv-item index=other]
{"value": "[wpv-post-id]", "label": "[wpv-post-title]"},
[wpv-item index=last]
{"value": "[wpv-post-id]", "label": "[wpv-post-title]"}
</wpv-loop>
<!-- wpv-loop-end -->
[/wpv-items-found]
[wpv-no-items-found]{"value": "", "label": "No items found"}[/wpv-no-items-found]
[wpv-layout-end]
Please note how post IDs are used as the values for the options and post titles are used as the labels.
6. The next step would be to register a new custom shortcode "[show_output_subspecialties_options]" which was used in step 4.
( ref: https://toolset.com/documentation/adding-custom-code/how-to-create-a-custom-shortcode/ )
// shortcode to create a list of subspecialties options
add_shortcode( 'show_output_subspecialties_options', 'show_output_subspecialties_options_func');
function show_output_subspecialties_options_func() {
// get the ID of the parent specialty
$parent_id = do_shortcode("[wpv-post-id item='@specialty-provider.parent']");
// output of the view to show subspecialties related to a specialty
$view_output = do_shortcode('[wpv-view name="view-to-show-subspecialties-options-related-to-a-specialties" wpvrelatedto="'.$parent_id.'"]');
// return the output
return $view_output;
}
The above code snippet can be included through either Toolset's custom code feature ( ref: https://toolset.com/documentation/adding-custom-code/using-toolset-to-add-custom-code/ ) or through active theme's "functions.php" file.
It basically gets the ID of connected specialty with the current provider and passes it as a shortcode attribute "wpvrelatedto" in the shortcode of the view from step 5 and then returns the output.
( ref: https://toolset.com/documentation/user-guides/views/passing-arguments-to-views/ )
7. Now that this second form is visually ready, it can be inserted below the first one in the view from step 1.
However, if you'd like it to show only once, a specialty has been selected through the first form, it will need to be wrapped within a conditional block.
( ref: https://toolset.com/documentation/user-guides/conditional-html-output-in-views/ )
It possible to get the ID of a specialty connected to the current provider in the view, using the "item" attribute:
( ref: https://toolset.com/documentation/user-guides/views/views-shortcodes/item-attribute/ )
[wpv-post-id item='@specialty-provider.parent']
This shortcode can be used in a conditional block so that the inner content (in this case the second edit form) is only shown if a post ID of a connected specialty exists.
[wpv-conditional if="( '[wpv-post-id item='@specialty-provider.parent']' ne '' )"]
<strong>Form to Select Subspecialty:</strong>
[cred_form form='form-to-edit-a-provider-select-subspecialty' post='[wpv-post-id]']
[/wpv-conditional]
Screenshot: hidden link
As a result, the second form will start showing below the first one, once a specialty has been selected.
Screenshot: hidden link
8. At this point, the options for the subspecialties will be available, but they'll not be linked to the current provider when this second form will be submitted.
To make this connection on form's submission, we'll need a custom function attached to "cred_save_data" hook:
https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data
// function to process subspecialty relationships with providers
add_action('cred_save_data', 'subspecialty_processing_action',10,2);
function subspecialty_processing_action($post_id, $form_data)
{
// if a specific form
if ($form_data['id']==1234)
{
// delete the existing connection between provider and subspecialty
// get existing connection
$existing_connections = toolset_get_related_posts($post_id,'subspecialty-provider','child');
if(!empty($existing_connections)) {
// delete the found connection
toolset_disconnect_posts( 'subspecialty-provider', $existing_connections[0], $post_id );
}
// if any option for a subspecialty is selected connect it to the provider
// if any option for a subspecialty is selected
if(!empty($_POST['select-subspecialty'])) {
// connect the selected subspecialty with the provider
toolset_connect_posts( 'subspecialty-provider', $_POST['select-subspecialty'], $post_id );
}
}
}
The above code snippet can be included through either Toolset's custom code feature ( ref: https://toolset.com/documentation/adding-custom-code/using-toolset-to-add-custom-code/ ) or through active theme's "functions.php" file.
Please replace "1234" with the actual ID of the second form and "subspecialty-provider" and "select-subspecialty" with the actual slugs of your post relationship and the generic field used in the second form, respectively.
When the form will submit, this function will remove any existing relationship between the current provider and any subspecialty and will connect the newly selected subspecialty instead.
You can learn more about the "Post Relationships API" functions used in this snippet from this reference guide:
https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/
9. One last step needed to complete the functionality of this second form would be to make sure that it shows the radio option for any existing connection between the current provider and a subspecialty checked, by default.
For this, you'll need some custom script, which can select the radio option, for the subspeciality which is already connected to the current provider.
<script type="text/javascript">
jQuery(document).ready(function () {
jQuery('input[type="radio"][name="select-subspecialty"][value="[wpv-post-id item="@subspecialty-provider.parent"]"]').attr('checked', 'checked');
});
</script>
This script can be included right below the shortcode of the second form.
Screenshot: hidden link
Using the same logic and techniques, you can build a third editing form that will include two "checkboxes" type generic fields, one for the "Conditions" and the other for the "Treatments".
I hope this helps and please let me know if any step is not clear.
If you need more personalized assistance around custom code, you can also consider hiring a professional from our list of recommended contractors:
https://toolset.com/contractors/
regards,
Waqar
