This thread is resolved. Here is a description of the problem and solution.
Problem: I have a Types termmeta (taxonomy) image field that includes an SVG image. When I try to display the image in a taxonomy View using a Types termmeta field shortcode in the loop, the SVG image is not displayed unless I include other information in the loop.
Solution: SVG images without explicit height and width attributes may not be displayed as expected. For best results, choose one of the preset image sizes like "thumbnail", then add CSS classes to set height and width of the rendered SVG image.
Relevant Documentation:
https://toolset.com/documentation/customizing-sites-using-php/functions/
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 4 replies, has 2 voices.
Last updated by 3 years, 10 months ago.
Assisted by: Christian Cox.
Okay the strange behavior you are seeing here is not directly related to Views' Query Filters, or even Toolset, really. It has to do with the fact that you're using an SVG file as the image tag source but no size attributes applied to the image tag. Use the browser inspector to check the View contents before and after removing the other shortcoees. The image tag is still present when you remove the other elements from the loop. Take a look at my screenshots here. You can see in the browser inspector when I remove all the content from the View's loop except one SVG image tag, the image disappears. If I then add an explicit height and width to the image tag, the image reappears.
So I think the strange behavior here is related to markup, CSS, and HTML rendering of SVG elements. Once the image size issue is fixed, you should see more predicatable behavior when manipulating Views filters. I would try setting explicit height and width values in the Types termmeta shortcode using pixels or percentages, or use a CSS class to define the size of this image.
I feel like I would love to understand how to combine different aspects of Taxonomy Term Filters (and Post Filters) as I believe this could be the solution. Specifically the "Set by URL" and "Set by ID" parameters combined with the ID, or SLUG shortcodes?
These dynamic options allow you to use the same View to display a termmeta field from different terms. "Terms with ID set by the URL parameter:" means that you determine which term will be included in the View results based on a URL parameter, like "termsfilter". The "termsfilter" part is arbitrary, it's whatever name you choose to use for the URL parameter. Let's say you configure the Query Filter to respond to a URL parameter "termsfilter". You can pass different term IDs into the URL parameter to influence which term will appear in the View results. Say your taxonomy has 3 terms with IDs 123, 234, and 345. The URLs you would use on the site would be:
https://yoursite.com/page-with-view/?termsfilter=123
https://yoursite.com/page-with-view/?termsfilter=234
https://yoursite.com/page-with-view/?termsfilter=345
Each of those URLs would produce different results in the View, so different termmeta fields would be displayed on the page.
"Terms with ID set by a shortcode attribute" is a similar in that it is a way to display different results dynamically, but instead of using URL parameters to determine which term will appear in the results of the View you use shortcode attributes:
[wpv-view name="Your Taxonomy Term View" termsfilter="123"] [wpv-view name="Your Taxonomy Term View" termsfilter="234"] [wpv-view name="Your Taxonomy Term View" termsfilter="345"]
Again, termsfilter is arbitrary. You can also combine shortcodes in this approach, like so:
[wpv-view name="Your Taxonomy Term View" termsfilter="[some-custom-shortcode][/some-custom-shortcode]"]
This would allow you to pass in the term ID based on some other custom shortcode.
