Solution:
No.
But, you can re-use Fields, when you add a new Group and choose what fields to insert, you will see there is an option to "Choose from previously created fields".
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);
Problem: I have two custom taxonomies, TaxA and TaxB. I would like to create a filtered list of posts organized by taxonomy term in a nested format where TaxA is the top-level structure, with all TaxB terms nested inside each TaxA term, and filtered posts displayed beneath TaxB terms.
Solution: Use a series of nested Views filtered by shortcode attributes.
Problem: It seems that a new Child Form on the parent post page does not properly assign the parent post. The parent appears to be selected, but not saved.
Solution: There is currently a known issue where new child post forms displayed on a page with a Layout are not assigning parents correctly. The following code snippet will work around the issue until a fix is ready:
add_action('cred_save_data', 'toolset_fix_layout_relationship_bug',10,2);
function toolset_fix_layout_relationship_bug($post_id, $form_data) {
// one array for each form
$hash = array(
array(
'id' => 282,
'slugs' => array('profile-service'),
),
);
// closure to find the matching array hash item and slug
$find = function( $var ) use ($form_data)
{
$el = ($var['id']==$form_data['id']);
return $el;
};
// create an array of form IDs where you want to apply this code
$forms = array_column( $hash, 'id' );
if ( in_array( $form_data['id'], $forms ) )
{
// find the slug array in the matching hash item and use it to connect the parent post
$thisHash = array_filter( $hash, $find );
$slugs = $thisHash[array_keys($thisHash)[0]]['slugs'];
foreach( $slugs as $slug ) {
$parent_id = $_POST['@' . $slug . '_parent'];
$parent = toolset_connect_posts( $slug, $parent_id, $post_id );
}
}
}
Problem:
After saving a content layout, my empty paragrpah tags in the editors, are not seen anymore on the front end.
Solution:
This issue is related to P tags being added in the front end if saving the post in the native WordPress Editor AND having a Content Layout assigned.
For this there are functions of Layouts that remove them, those are the same functions that remove the empty tags you add intentionally.
Note, it's not a good practice to add empty prargraphs to add space or lines.
We will work on improvements related to this, however we also suggest not using empty HTML P tags…
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
