In my Toolset archive search, the search form reloads during pagination, undoing modifications made by jQuery. This issue particularly affects a collapsible and expandable terms feature I'm using.
Solution:
Adjust your jQuery code to record the state (expanded or collapsed) of each term in an array or object. Upon the ajaxComplete event, use this recorded state to maintain the terms' status after pagination.
The user had three custom post types (cpt1, cpt2, cpt3) and a custom field group called "cf" assigned to each of them. They wanted to use the same form for all custom post types to submit data from the frontend. However, Toolset only allows a separate form for each custom post type.
Solution:
-Create separate forms for each custom post type (cpt1, cpt2, cpt3).
- Go to Toolset > Content Templates and create a new Content Template, without assigning it to any post type (e.g., name it "conditional-logic").
- In the Content Template, use Conditional Blocks and Forms Blocks to create the desired conditions for each custom post type. For example:
[php]
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt1' )"]
[shortcode for the form for cpt1]
[/wpv-conditional]
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt2' )"]
[shortcode for the form for cpt2]
[/wpv-conditional]
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt3
[/wpv-conditional]
[/php]
The user needs to update the 'book-url' custom field value for all posts of the 'book' post type without having to edit each post individually.
Solution:
You can use a code like this:
[php]function update_book_urls($post_type, $url) {
// Get all posts of the 'book' post type
$args = array(
'post_type' => $post_type,
'posts_per_page' => -1,
);
$book_posts = get_posts( $args );
// Loop through each post and update the 'book-url' custom field
foreach ( $book_posts as $post ) {
update_post_meta( $post->ID, 'wpcf-saas-deal-link', $url );
}
}
update_book_urls('saas', 'https://book.com');
[/php]
I have a custom field group where I have bunch of custom fields. If I change the slugs of the custom fields, will it create any issue, like data loss of the custom fields?
Solution:
Yes, it can produce some issues - which can be resolved, but perhaps it'll be a costly manual labor. For instance:
- we have an image field on a content template
- we go to the Custom Field group of this image field
- change its current slug ('image') to anything different -> 'image-test', for example
After this change, we'll check that the image displaying on the content template just disappears. Because it still thinks that the slug is 'image' - therefore, we would need to select the image field again, in order to make the system recognizes the new slug. Please check the screenshot: https://snipboard.io/rYb0Pl.jpg
This will happen to any field that you change its slug. If you have several fields, you'll need to re-select all of them and maybe it would be a extensive manual work.
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.
