Contact Form 7 Translate Messages Extension vs HDForms | Contact Form Builder

Translate default Contact Form 7 messages without changing WordPress profile language. Default supported languages: AR, BEL, BG, CA, CS, DA, DE, EL, EN-AU, EN-CA, EN-GB, EN-NZ, EN-ZA, ES, ES-AR, ET, FA, FI, FR, FR-CA, GL, HR, HU, IT, JA, KO, LT, NB, NL, NN, PL, PT, PT-BR, RO, RU, SK, SQ, SV, TR, UK, VI, ZH-CN, ZH-TW How to add more languages: To add languages, you have to download translations from the official page of Contact Form 7 on translate.wordpress.org. Click on a language and a new page will open. Always choose the “Stable (latest release)”. Another page with all the string translations will appear, scroll down to the end of the table and just under the Legend, click on “Export as JSON”. Move the downloaded translations files to /your-theme/cftmsg_translations folder (create it if does not exists).

HDForms. The easiest way to create contact forms HDForms was designed and built to be a super easy system to create contact forms of any size. The forms are automatically validated for user input, sanitized for security, and, of course, sent without fuss! HDForms comes with an easy to use visual form builder, and can be used for small contact forms, intake forms, request for quotes, or large applications. With HDForms, you can even intelligently show or hide certain fields with ease – no coding required! Video A video is currently being made that will highlight just how easy HDForms is to use. Check back soon! Features include 👍 Super easy to use (I really can’t express enough how easy HDForms is to use) Will work with just about any well-coded theme right out of the box Mobile-friendly (responsive design) Form builder (block based) Column support Custom toggles and triggers to show/hide elements Emails are automatically built and validated Automatic spam protection Run your own function before and after form submit (for you devs out there!) Pretty 🙂 Pretty much all of the standard features required for a form builder, with more options coming soon. Upcoming Features ⏳ The following features are not yet included in HDForms, but are on the road map for future updates. Some of these features will be finalized in the next couple of weeks, others may be months down the line. This list is not in order of importance. File uploader element Better localization (for things like the phone number, date, and currency fields) Translation ready. Sorry! English only for now 🇨🇦 ❓ HOW TO USE | TUTORIAL ❓ Full tutorial and documentation is still being written. This section, along with a link to the full documentation will be updated ASAP. Once a form has been created and saved, you can use the build-in Gutenberg block, or you can just copy and paste the shortcode anywhere on the site to render the form. You can also use WordPress’s do_shortcode() function to render the form: Triggers You can view the HDForms About / Options page to see an example of how triggers and toggles work. Setting up triggers is by far the most complicated thing to do, but I hope that this quick tutorial will help. You’ll need to know two things in order to create triggers. The trigger element, and the toggle element. The trigger element is the element that we check if its input has changed, and the toggle element is the element we either show or hide. In the above example, the trigger element is the checkboxes (specifically the one for “other”), and the toggle element is the text input. In HDForms, each element you create gets a special and unique ID. You can find this ID by selecting the element to edit it. You’ll need to get the ID of the trigger element and paste it into the toggle element’s “Trigger Element” field. That’s it! By default, the toggle element will remain hidden unless the trigger element gets some data. But what about, for example, like above, where I only want the toggle to happen if a certain checkbox is selected? In this case, we also want to pass along what “option” we want the trigger to work on (note: this is only for radio or checkboxes). This can be easily done by adding [x] to the end of the ID, where x is the number of the option. So in the above example, “other” is the fourth (4) listed option, so I would append [4] to the end of the ID. A full example trigger element id might look something like this hdf_3481_checkbox_oxpkhp[4]