Images on the frontend were opening the media page even though the image link option had been set to “None”.
Solution:
The frontend content was not coming from the main WordPress editor. It was being loaded from a WYSIWYG custom field named editor, used by the View. The image links were still present in that custom field. After removing the link from the correct custom field, the frontend reflected the change. Future edits need to be made in that custom field, not in the main page content.
I want to display nested repeatable fields in Toolset to show a tour schedule of a recording truck with cities, each having multiple locations and schedules. I was unsure how to implement this using Toolset Views and Repeatable Field Groups.
Solution:
Enable legacy Views, then create a nested structure with two Repeatable Field Groups—Cities and within each, Locations. Use two nested Views: one for Locations and one for Cities, filtering by parent post, and embed them in the Content Template for the main "Stations" post.
I want to associate each album with an author and display the author's name as a clickable link that directs to their custom post page.
Solution:
The best approach is to create a one-to-many post relationship between the Author and Album post types. This allows you to select an author directly within the album post. Then, using a Toolset View, you can retrieve and display the related author’s title with a link to their page.
Two grids with single fields are causing duplication issues when the second row is conditional. The second field in red is duplicated in the first one (in blue).
Solution:
- Check for HTML code inside conditionals that might cause errors, especially unclosed tags.
- Verify the conditional logic and ensure it works correctly according to the documentation.
- Make sure you select the year, month and date in the date picker, then click the update button to save the post.
Problem:
The user has a grid view that should display 2*3 elements, and it was displaying 3 rows with (3,2,1) columns.
Solution:
The issue was caused by a nested <em> HTML tag in the custom field used inside the loop of the view. That breaks the validity of the whole view and Toolset generated an undesired grid.
Once we removed the child "em" tag, the issue was fixed.
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.
