The issue here is that the user wanted to delete his posts using the front end. Solution:
This requires that you add the CRED delete link to the post on the front end.
To do this edit the content template assigned to the post and the click on the CRED form button. Finally just insert the delete link and this should allow you to delete the posts from the front end.
The issue here is that the user wanted to automatically send notification to his parent cpt.
Solution:
What you can do is to create a cpt called Jobs, and Job Application.
Set the Job CPT as the Parent of the Job Application. Now on the Jobs CPT you can create an email field so that the recruiter can post a Job and the email that the Job applications should be sent to.
Then Create a CRED form for your Job Applications and then add the CRED form child post link to your Jobs, if you are using a content template then you can simply just add the child post form link to the there.
On your child post form you can add a generic field like this.
Then create a notification for this field in CRED.
Finally you will need to add this hook to your functions.php which will copy the Email from the Parent Job into the child post being created so that the notification will be sent to the person who created the job.
add_action('cred_before_save_data', 'my_before_save_data_action',10,1);
function my_before_save_data_action($form_data)
{
// if a specific form
if ($form_data['id']==2981)
{
if(isset($_POST['_wpcf_belongs_job_id']) and $_POST['_wpcf_belongs_job_id']!=""){
$parent_post_id = $_POST['_wpcf_belongs_job_id'];
$x = get_post_meta($parent_post_id,'wpcf-job-email',true);
$_POST['parent-email'] = $x;
}
}
}
In the code above I create 3 things: 1. CPT called Jobs with the slug job, you can see i'm getting the ID of the parent Job by referencing is with "_wpcf_belongs_job_id" If you're using a different slug you will need to replace all instance of "_wpcf_belongs_job_id" with "_wpcf_belongs_{parent-cpt_slug}_id" where you will replace the {parent-cpt_slug} with the slug of your CPT
2. I made a custom field on the Job CPT called "Job Email" which gets a slug "job-email". I referenced this field with "wpcf-job-email". In your case when you create the field you will reference it by add the "wpcf-" prefix to the slug and replaceing all instances of "wpcf-job-email"
3. Finally I made the generic field "parent-email". If you use the generic field code that I sent then you can leave this as is.
Problem:
The issue here is that the user wanted send Emails to an email address that is stored on his parent posts when his child posts are created.
Solution:
What you can do is to create a cpt called Jobs, and Job Application.
Set the Job CPT as the Parent of the Job Application. Now on the Jobs CPT you can create an email field so that the recruiter can post a Job and the email that the Job applications should be sent to.
Then Create a CRED form for your Job Applications and then add the CRED form child post link to your Jobs, if you are using a content template then you can simply just add the child post form link to the there.
On your child post form you can add a generic field like this.
Then create a notification for this field in CRED.
Finally you will need to add this hook to your functions.php which will copy the Email from the Parent Job into the child post being created so that the notification will be sent to the person who created the job.
add_action('cred_before_save_data', 'my_before_save_data_action',10,1);
function my_before_save_data_action($form_data)
{
// if a specific form
if ($form_data['id']==2981)
{
if(isset($_POST['_wpcf_belongs_job_id']) and $_POST['_wpcf_belongs_job_id']!=""){
$parent_post_id = $_POST['_wpcf_belongs_job_id'];
$x = get_post_meta($parent_post_id,'wpcf-job-email',true);
$_POST['parent-email'] = $x;
}
}
}
In the code above I create 3 things:
1. CPT called Jobs with the slug job, you can see i'm getting the ID of the parent Job by referencing is with "_wpcf_belongs_job_id" If you're using a different slug you will need to replace all instance of "_wpcf_belongs_job_id" with "_wpcf_belongs_{parent-cpt_slug}_id" where you will replace the {parent-cpt_slug} with the slug of your CPT
2. I made a custom field on the Job CPT called "Job Email" which gets a slug "job-email". I referenced this field with "wpcf-job-email". In your case when you create the field you will reference it by add the "wpcf-" prefix to the slug and replaceing all instances of "wpcf-job-email"
3. Finally I made the generic field "parent-email". If you use the generic field code that I sent then you can leave this as is.
Problem: I have a problem showing the search and results sections of my View in two different parts of the page. When I place the View using two shortcodes, the search filters appear, but not the results. If I use a single shortcode to place the same View, both filters and results appear.
Solution: There is a problem in the markup of this View's Filter Editor panel. There is a div tag left unclosed, which results nested form tags when two separate Views shortcodes are used. Check your Filter Editor markup to confirm your HTML code is properly structured.
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.
