High-DPI (retina) Apple displays made gallery images look soft: a 250 px image placed in a 250 px container was effectively upscaled (should be 500 px for 2× density).
Solution:
Use WordPress’s responsive images with srcset/sizes: upload originals at ≥2× the largest CSS display size; output images via standard (not CSS backgrounds) so WP generates srcset. In Toolset, use dynamic Image blocks or image shortcodes that output HTML (e.g., [types field="artwork-image" size="large" output="html"][/types] or [wpv-post-featured-image size="large"]), letting retina browsers pick higher-resolution candidates automatically.
I needed front-end forms under “Gallery/Corrections/Subscribed” that only logged-in “Listivo User” members could see/use, and each user should edit only their own submissions linked to an Event; forms were visible to guests and/or users could edit others’ content.
Solution:
Create a separate XYZ post type related one-to-many to Event; build add/edit Forms for XYZ (with a hidden relationship field set to the current Event and post author = current user), use a View + Conditional to show “Add” if no XYZ exists for the user or “Edit” otherwise, and fix permissions in Toolset → Access for the XYZ post type and each Form so only logged-in “Listivo User” can add/edit their own items.
I wanted to add category (taxonomy) filters to a WordPress Archive built with the block editor; I could add a search, but wasn’t sure if taxonomy filters were possible in Toolset Blocks.
Solution:
In the Archive editor (Toolset → WordPress Archives), select the Archive block, click “Add Search Field,” choose “Post Taxonomy,” pick the taxonomy (e.g., Categories), select the input type (checkboxes/select/radio), and configure options and AJAX update in Custom Search settings.
I ran a local site on WordPress Studio (SQLite) and hit a fatal error during Toolset’s upgrade when it tried to ALTER TABLE wp_toolset_relationships to add the autodelete_intermediary column (duplicate column error), preventing access to the admin side.
Solution:
This environment isn’t supported by Toolset; the fix was to use a standard WordPress stack with MySQL/MariaDB (e.g., MAMP/WAMP/Local WP/XAMPP) or migrate to a regular host, after which the issue no longer occurred.
I couldn’t update my site even though my Toolset license was active; it showed the error “Unable to register: Site key not matching.”
Solution:
Unregistered and re-registered Toolset via WordPress Dashboard → Plugins → Add New → Commercial tab → Unregister Toolset → Register Toolset → Get a key for this site → paste the new key and confirm. This resolved the license mismatch error.
