The customer reported multiple deprecation warnings when using Toolset with WordPress 7.0. The warnings showed that several Toolset blocks were still registered with Block API version 1 and that deprecated WordPress functions were being used.
Solution:
It was confirmed that Toolset does not currently support the newer block API requirement mentioned in the warnings. The ticket was forwarded internally as a feature request so it can be tracked and help increase development priority.
The customer wanted a Toolset map to show different marker icons based on a post’s taxonomy term, while keeping the marker popup functionality.
Solution:
The solution was to remove the default marker from the Map block settings and add
[wpv-map-marker]
shortcodes manually inside the View loop, wrapped in
[wpv-conditional]
checks for each taxonomy term. The popup content remains available inside the marker shortcode. The customer confirmed it worked. They also noted the earlier issue was likely caused by using two separate HTML blocks inside the loop, one for the marker and one for the post information.
The customer wanted to change an existing Toolset relationship from one-to-many to many-to-many so one event could be connected to multiple partners, and wanted to know whether this could break existing relations.
Solution:
The change is possible, but it should be done carefully on a staging site. Existing event-partner connections need to be checked after the change, and any Views, Forms, templates, or custom code depending on the old one-to-many structure may need updates. It was also noted that many-to-many setups may require an intermediary post type when relationship fields are needed.
