The customer’s site appeared to be connected to Toolset, but plugin updates were not showing on the website.
Solution:
The recommended fix was to manually update the Toolset plugins first, then refresh the site registration by unregistering and registering the site again from the Commercial tab using a newly generated site key. This ensures the site connection is current and allows updates to come through correctly.
The customer wanted to display a Toolset YouTube block in vertical 9:16 aspect ratio, but the block settings only offered horizontal aspect ratios. A CSS workaround did not achieve the desired result.
Solution:
It was explained that Toolset does not provide a built-in 9:16 option and that this cannot be added to the block’s Aspect Ratio selector through supported settings. The workable alternative was to use a third-party video shortcode that supports vertical videos, store the YouTube URL in a Toolset custom field, register the shortcode under Toolset → Settings → Front-end Content → Third-party shortcode arguments, and render it in a Toolset context such as a Fields and Text block or a Content Template. The custom field value could then be passed into the shortcode attribute.
The customer wanted to prevent a user from creating more than one Profile post, while still allowing the same user to create multiple Event posts.
Solution:
There is no single setting for this, but it can be controlled per post type. The recommended approach was to show the Create Profile form only when the logged-in user does not already have a Profile post. This was done by using a View filtered by post author equals the logged-in user, and placing the profile creation form inside that View’s loop template. This limits Profiles to one per user without affecting Event creation.
The customer could not register the Toolset site key. Even though the domain and key looked correct, the website kept showing that the key was wrong. The site was also running a very old version of Toolset Types.
Solution:
The issue was caused by using an outdated Toolset version. The recommended fix was to manually update the Toolset plugins to the latest version first, and then unregister and register the site again from the Commercial tab using a newly generated site key. This resolves the registration problem on old Toolset installations.
