matthewL-7
Support threads created in the last 30 days: 0
Favorite Forum Topics
This user has no favorite topics.
Forum Topics Created
Status | Topic | Supporter | Voices | Posts | Freshness |
---|---|---|---|---|---|
Container not working correctly on tablet size screen
Started by: matthewL-7 in: Toolset Professional Support |
2 | 2 | 5 years, 11 months ago | ||
Can I use conditional output with a repeatable field group
Started by: matthewL-7
in: Toolset Professional Support
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. Relevant Documentation: |
2 | 7 | 6 years ago | ||
Conditional formatting not working how I would expect
Started by: matthewL-7
in: Toolset Professional Support
Problem: I'm trying to test if the post type single name is equal to a specific string, but it's not working as expected: [wpv-conditional if="( [wpv-post-type show='single'] eq 'Post' )" debug="true"]Test[/wpv-conditional] Solution: Try wrapping the wpv-post-type shortcode in quotes, then adjusting your nested quotes like this: [wpv-conditional if="( '[wpv-post-type show="single"]' eq 'Post' )" debug="true"]Test[/wpv-conditional] Relevant Documentation: |
2 | 3 | 6 years ago | ||
Include search box with search query in it
Started by: matthewL-7 in: Toolset Professional Support |
2 | 2 | 6 years ago | ||
Resizing images
Started by: matthewL-7 in: Toolset Professional Support |
2 | 4 | 6 years ago | ||
Conditional output based on last modified date
Started by: matthewL-7 in: Toolset Professional Support |
2 | 6 | 6 years ago | ||
Read more link being inserted in excerpt
Started by: matthewL-7 in: Toolset Professional Support |
2 | 5 | 6 years ago | ||
Content templates not working correctly
Started by: matthewL-7 in: Toolset Professional Support |
2 | 6 | 6 years, 1 month ago | ||
Review feature
Started by: matthewL-7 in: Toolset Professional Support |
2 | 3 | 6 years, 2 months ago | ||
Show custom field in filter dropdowns
Started by: matthewL-7 in: Toolset Professional Support |
2 | 4 | 6 years, 2 months ago | ||
Filter drop down using custom field
Started by: matthewL-7 in: Toolset Professional Support |
2 | 2 | 6 years, 3 months ago | ||
Showing a custom field in replacement of the default page title
1
2
3
Started by: matthewL-7 in: Toolset Professional Support |
2 | 36 | 6 years, 3 months ago | ||
Paginated lists cleaner URLs
Started by: matthewL-7
in: Toolset Professional Support
Problem: The issue here is that user wanted a clean url on their AJAX Pagination. Instead they are getting wpv_aux_current_post_id=22356&wpv_view_count=22393-TCPID22356&wpv_paged=2 Solution: Actually no it's not possible, however you can disable the url completely by using the AJAX pagination and then go to Toolset-> Settings -> Frontend Content and then disable the browser history management. |
2 | 7 | 6 years, 4 months ago | ||
Custom field data not saving
Started by: matthewL-7
in: Toolset Professional Support
Problem: The issue here is that the user's custom fields are not saving the data. This is actually a known issue and was resolved in our latest types version 3.0.4 |
2 | 5 | 6 years, 5 months ago | ||
Shortcode from HTML Sitemap plugin
Started by: matthewL-7
in: Toolset Professional Support
Problem: The issue here is that the user is unable to see their sitemap on their page. Solution: This happened because there was an empty content template assigned to the page. The quickest way to resolve this is to add the [wpv-post-body] shortcode to your content template. |
2 | 8 | 6 years, 5 months ago |