Hi Marco,
Thank you for contacting us and I'd be happy to assist.
> How can I use required fields on form 1 and not show them on form 2, form 3 etc?
- As you observed, when a user custom field is set as required through the field settings, it can't be dropped from any user form.
To achieve what you're planning, you can set all those user fields as 'not required'.
Then in any particular form where you have to make them required, you can include custom JS script to make them required, selectively.
> What to do with the username, password, email etc fields hidden link. I now set them to auto generate on all forms.
- If you don't want these 3 user fields to appear in the user edit form, you can just keep their respective checkboxes checked for autogeneration.
If unchecked, those fields will also appear in the edit form, available for editing. The exception is a 'username' field, which will be read-only, as it can't be changed.
> Do I always have to translate all message files? Isn't there a way of placing a .po and .mo in languages?
- To globally translate the form messages, you can use the 'wp-cred.po' file available at the folder:
/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/locale/orig/
> I will be using Woocommerce for payment. How can I use the right user info in checkout? Now the address fields are not assigning to billing fields. I have created new fields in Toolset.
- The WooCommerce plugin stores the address field data in its custom fields, which can't be directly linked with the user fields added through the Toolset Types.
If you don't want to store the addresses in duplicated/repeated fields, you can remove them from Toolset user fields. Next, you can use the field slugs used by WooCommerce address fields, in generic fields in Toolset user forms, so that the data is stored in the same fields.
Here is a thread with the details of an example usage with a similar requirement:
https://toolset.com/forums/topic/woocommerce-fields-in-user-form/
I hope these points will help and let me know if you have any follow-up questions.
For future reference, we encourage creating a separate ticket for each question or concern, for the most efficient support.
regards,
Waqar