Problem:
The customer wanted to make certain buttons on their website full-width to ensure a consistent and appealing layout across different parts of the site. Solution:
We advised applying a CSS rule (width: 100%;) to make the buttons full-width. This rule was suggested to be added to the .tb-button__link selector to affect all buttons globally or to specific buttons using data attributes to restrict the changes to buttons shown in the provided screenshot:
Option 1:
Problem:
The customer faced an issue where a required checkbox added to a Toolset user registration form was not visible on the front end—only the label was showing. Additionally, they needed guidance on placing an explanation text beside the checkbox, as the default label positioning placed the text above the checkbox. Solution:
We resolved the visibility issue by adding a space to the checkbox slug, which allowed it to appear correctly on the front end. For positioning the explanation text beside the checkbox, we suggested including the text directly within the checkbox slug, ensuring it displayed as intended. To further customize the slug, allowing HTML for linking within the checkbox label, we applied a workaround from the Toolset documentation that permits HTML content in field labels. Relevant Documentation: https://toolset.com/errata/html-in-toolset-custom-field-labels-is-stripped-when-saving-the-fields/
Problem: I am trying to translate specific messages in the Toolset Forms plugin without using the WPML plugin, and I need help finding the correct text domain for gettext filter usage.
Solution: Use the Toolset Forms plugin's dynamic text domain which depends on the ID of your form. For example, if the ID is 1553, the text domain would be "toolset-forms-1553". To find the ID for default forms like [wpv-forgot-password-form], check the same location where custom form IDs are listed, or use the WordPress "gettext" filter directly if you prefer not to use a text domain.
