Just install it, then go to your taxonomy link, the "Taxonomy order" link should be below it or at the end of the sublinks. Enter it and reorder your terms. They will, then, be ordered in the form too. Check these screenshots:
- Link for configuration: http://prntscr.com/urah16
- Reorder with drag/drop: http://prntscr.com/urahkw
- Results on the frontend: http://prntscr.com/urair7
Problem:
The user would like to have an OR relation in a condition.
Solution:
You can use the user interface to create the conditions.
You can nest expression but you cannot use OR on values. OR/AND/etc. are used between expressions:
Problem: I would like to use Forms to allow Users to submit and edit posts. I would like to group Users by Company, and allow all Users from the same Company to read and edit all posts by all Users from the same Company.
Solution: Unfortunately there isn't a simple option that will allow you to create this type of filter. I think the simplest option is to add a custom field that holds a Company ID in the User profile, and add another custom field that holds the Company ID in each post. When each User submits content, the Company ID from their User profile could be used to set a custom field in the submitted post. Then you could filter a View by Company ID, and that would show each User content from other Users in their own Company.
Another more complex solution is to use a proxy custom post type that represents Users - something like "Employees". Each User is the post author of one Employee post. Then you can use post relationships to relate Employees and Companies. Then you can use Views post relationship filters to show and hide content based on which Company the Employee is related to. We have more information about using a proxy post type available here: https://toolset.com/documentation/post-relationships/how-to-create-custom-searches-and-relationships-for-users/
See the first FAQ for more information about how you can limit each User to only one Employee post.
Problem: I would like to redirect Users from Forms to archive pages.
Solution: Use the cred_success_redirect API to redirect to other URLs:
add_filter('cred_success_redirect', 'custom_archive_redirect_for_forms', 10, 3);
function custom_archive_redirect_for_forms( $url, $post_id, $form_data )
{
// update this hash to include one line for each form ID and its respective redirect destination URL
$redirect_for_forms = array(
'f123' => 'https://yoursite.com/some/archive/url',
'f234' => 'https://yoursite.com/some/other/url',
'f345' => 'https://yoursite.com/yet/another/url'
);
// ----- You should not edit below this line ------
// test if the array key exists first, then return the proper URL if the form ID is found in the hash
if( array_key_exists( 'f'.$form_data['id'], $redirect_for_forms ) ) {
return $redirect_for_forms['f' . $form_data['id']];
}
// otherwise, just return the original destination url
return $url;
}
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.
