Problem: I have a custom field on User profiles. I would like to write a conditional that tests whether or not any content exists in the field for the current author archive User.
Problem:
Can I hide or show parts that are not the content of my theme (widgets, header, footer, etc) depending on a view's output or similar?
Solution:
Only applying custom code, since the Theme's parts mentioned (widgets, header, footer, etc) are part of the theme and not the content (the_content()) which can be styled and edited with Toolset.
You would need to create a Child or Custom Theme and hide/show the sections according to results received from PHP calls to the Views or other data providers used.
Problem: I have a View of a hierarchical taxonomy. All the terms in the taxonomy are displayed in the View, but I want to show only the top-level terms. No child terms should be shown.
Solution: Use a term parent Query Filter set to parent term is "None". This will show only top-level terms.
The issue here is that the user wanted to prevent their Toolset form from being submitted unless the user clicks yes to a Popup question after clicking submit.
Solution:
This can be done by using the JS below.
jQuery(document).ready(function(){
$("input[name='form_submit_1']").click(function(event){
event.preventDefault();
if (confirm("Are you sure you want to report this offer as broken?")){
jQuery('form#cred_form_28499_1').submit();
}
});
});
This will prompt the user with a question and only submit the form once the user answers yes to the question.
Problem: I have a repeatable field group that contains several fields. I would like to use a conditional to test if any of the RFG has a value in one specific field. If so, I would like to show some text in a header. If not, I would like to hide the header.
Solution: One way to accomplish this in Toolset alone is with a View of the Repeatable Field Group. Add a post relationship query filter, so that the parent post is set by the current page ( or the current post in the loop if you're displaying the main post in a View ). Then add a Query Filter for the custom field (or fields), and check that the field value is not empty. Set the limit to 1 post, since all you need to know is whether or not one exists. In the wpv-items-found section of the loop, add the heading information you want to display. In the wpv-no-items-found section, delete the text message. This View is now effectively a conditional that tests if any related RFG have content in the custom field(s) in your query filter.
If you need something more flexible, a custom shortcode approach is probably more practical. You can use the toolset_get_related_posts API to get all the RFGs for a specific post, then loop over them and inspect their post meta values. I can help with toolset_get_related_posts if you need more information. Basically an RFG is treated as a child of the main post. The slug of the relationship is identical to the RFG slug.
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.
