Solution:
In order to use this not recommended approach, Views actually adds a own ShortCode parser to allow things like this, but you have to be careful with brackets and outputs.
What is sure, your URL's will not work with double apostrophes.
Problem:
The Child Field is shown instead of the Parent Field, in a View querying Child Posts.
Solution:
The issue is always the same in this case.
1. The Parent Post information you want to display is not existent or not connected to the Child Post queried in the View
2. The Parent info is not called correctly
After reviewing the above mandatory settings, you can avoid to fallback to the Currently Queried Post's field by evaluating first if the Parent Field exists.
If not, display nothing.
Problem:
Filter the post view by publish date, which is setup by Views shortcode attribute.
Solution:
Views is using WordPress class WP_Query to query the post, see the document: http://codex.wordpress.org/Class_Reference/WP_Query#Date_Parameters
The days parameter of Views is correspond to "The day of the month", but in your case, it needs a strtotime()-compatible string, for example:
after 30 days ago
So it needs custom codes with Views filter hook to apply such a filter, I added below codes into your theme/functions.php:
Problem:
How to check if a field value has changed when submitting a CRED that edits a Post
And if changed, update/add some actions.
Solution:
1. Use the cred_before_save_data action, as otherwise the past is already updated when you compare.
2, This is a example code, fully commented:
function record_status_change($form_data)
{
// if a specific form
if ($form_data['id']==168) //CRED Form ID
{
//get existing post id
$existing_post_id = $form_data['container_id']; //Current CONTAINER of Form (current Post)
//https://toolset.com/documentation/user-guides/cred-api/#cbsd
//get existing post field value
$existing_post_status = get_post_meta($existing_post_id, 'wpcf-value', true); //Get post meta value of currnet post
//get new field value
$new_field_value = $_POST['wpcf-value']; //get value of current CRED Form field
//If value has changed
if ($existing_post_status != $new_field_value) //if this is not the same
{
//if, then insert the new post
//values please refer to this DOC:
//https://codex.wordpress.org/Function_Reference/wp_insert_post
//I already put in a few examples, it's to adapt. Please read the WP Codex carefully for debug.
$new_post = array(
'post_content' => '',
'post_excerpt' => '',
'post_name' => 'title',
'post_status' => 'publish',
'post_title' => 'title',
'post_type' => 'post',
'menu_order' => '');
//insert post
$new_post_id = wp_insert_post( $new_post );
//NOW Update the new posts fields! required.
//(it shoudl automatically create them if non-existent)
update_post_meta($new_post_id, 'your-new-custom-field-slug', 1);
}
}
}
add_action('cred_before_save_data', 'record_status_change',10,1);
3. This checks the FORM's fields value against the CURRENT posts (same field) value.
The FORM must be on the POST that is edited currently
Problem:
How to update another Custom field when a there is as given value in a custom field of current edited post
Solution:
1. use a cred_save_data action
2. Check if the Field's value is == value
3. If this is true do your custom actions.
4. This is a example code:
function position_filled($post_id, $form_data)
{
// if a specific form
if ($form_data['id']==168) //CRED Form ID
{
//get value of cv-status (Radio value of current CV Sent edited with CRED)
$new_cv_status = get_post_meta($post_id, 'wpcf-value', true);
//check if CV Status == 'Placed'
if ($new_cv_status == 7)
{
//get ID of parent Job , which is stored in the CV Status wpcf_belongs_job_id
$ID = get_post_meta($post_id, '_wpcf_belongs_parent-file_id', true);
//get the parent post object
$post_parent_object = get_post( $ID );
//get it's ID
$ID_parent = $post_parent_object->ID;
//Update the parent's post field (RADIO)
update_post_meta($ID_parent, 'wpcf-value', 1);
}
}
}
add_action('cred_save_data', 'position_filled',10,2);
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.
