Problem:
My HTML Conditional does not work, even though visually the syntax is correct and it should expectedly work.
This is the syntax example:
[wpv–conditional if="( '[wpv-post-taxonomy type='related' format='slug']' ne '' )"] NOTHING[/wpv–conditional]
Solution:
Sometimes it can happen that unexpected hidden formatted text gets copied when you copy the code from a Webpage.
It's a good idea to convert into plain text before inserting into the editors if you experience unexplainable failure of HTML conditions (and other HTML) in general.
Often it's good to just generate the conditions using the GUI if possible.
That'll ensure a pure output that is generated with bare text.
Problem:
Whenever I ues Custom ShortCodes in HTML conditionals, then the conditions fail, and do not even output debug information anymore if `debug="true"` is set.
Solution:
To use Custom ShortCodes (or ShortCodes of other Themes/Plugins) in HTML Conditionals, you need to register those ShortCodes first in Toolset > Settings > Front end content > Third-party shortcode arguments.
Problem:
How to output nothing from a View if there are no results?
Solution:
It's not necessary to use a conditional shortcode, you can simply remove everything in the wpv-no-items-found section of the View output.
If you have a heading or similar that you want to precede the View results and only show this when there are results to show, you can move the heading inside the View output section, within the wpv-items-found section but outside of the wpv-loop tags (otherwise it would be repeated for every result).
Problem: I have an embed custom field that is mostly used to store image URLs. I would like to be able to display those images, but the embed field displays a clickable URL. How can I display the image instead of its URL?
Solution: You could use the URL to generate an img tag on-demand, or you could convert the embed field to an image field.
I want to have the excerpt of my custom post type 'Directory' to always have the default initial value of the shortcode:
[types field='dir_item_description'][/types]
Problem: I would like to understand the advantages of using a single checkbox custom field as opposed to using a single term in a custom taxonomy. I would also like to know if it's possible to migrate a custom field checkbox to be a single term in a custom taxonomy.
Solution: The advantage of a checkbox vs. a taxonomy term are a bit subjective. When you create Query Filters in wp-admin, you can create more powerful filters for custom fields than you can create for terms, but in practical use that's probably not a real advantage. You could argue that it's less likely for other site admins to be able to create a problem by adding other terms to this custom taxonomy. It's also easier to set up a checkbox field that doesn't have a term archive associated with it, since taxonomy terms are usually set up to have archives by default. You can assign custom fields to a many-to-many relationship, while it's not always easy to assign a taxonomy term to that same relationship. Managing this checkbox status in Forms might be a challenge if it's set up as a flat taxonomy because there's no simple checkbox input for flat taxonomies. You would have to type the term name.
Those are the main things I can think of right now. Migrating a checkbox to a term would require custom code, a custom SQL statement that directly manipulates the database, or some manual intervention in a CSV export / import process.
Problem:
A select custom field lists all countries as options, but only some of these have been applied to posts. When creating a search View how to only include those countries in the filter dropdown which have been assigned to posts.
Solution:
In the Custom Search Settings select "Let me choose settings manually" and then choose "Show only available options for each input".
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
