Jay Mac asked 1 year ago
Walter Jones answered 1 year ago
Jay Mac
replied 1 year ago I am using the FF Registration Addon and yes the username field is the personal email and that is the one I am not allowing them to update (readonly). I have validated the org email is in the wp_user_meta table and the personal email that is the username is the wp_users table.
Jay Mac answered 1 year ago
Please login or Register to submit your answer
I'm not sure there's an answer to your question. I've been using Formidable for a very long time, and when I've had a requirement for a unique field, it just always works. I have no idea how Formidable tests for uniqueness. We're Community Volunteers and use Formidable as end users, just like yourself. This question is something I think only a developer intimately familiar with Formidable's Core code can shed some light on.
What did the AI suggest? What features are not available? Maybe we can help with that if there are references to hooks.
Thank you Victor. The userid that is set via the email is the personal email like a gmail account. The assumption is that people will not change that very often. I leave that alone. I add a second email their corporate or organization email that is stored in user_meta. They can change that as they switch jobs. I still want that email to be unique so it should be checked for duplicates. If I set unique and recall it from user_meta in a profile update form and the user does not change it the form will not submit saying the email must be unique. I thnk the AI assistant was confused but it did have a great answer using conditional logic options that are not on my form:
Maybe this quick answer from our AI Assistant will help?: To allow the user to not update a unique field, you can use a conditional logic rule in your form that checks if the unique field is already filled with the user's email address. If it is, then the field should be set to read-only, so that the user cannot change it.
Here are the steps to set up this conditional logic rule:
1. Go to the form builder and select the field that has the unique option checked.
2. Click on the "Advanced" tab in the field settings.
3. Scroll down to the "Conditional Logic" section and click on "Add Rule".
4. In the "If" section, select "Field" and choose the field that contains the user's email address.
5. In the "Is" section, select "Filled" to check if the user's email address is already filled in the field.
6. In the "Then" section, select "Field" and choose the unique field that you want to make read-only.
7. In the "Action" section, select "Read-only" to make the field read-only if the user's email address is already filled in the field.
8. Save the form and test it to make sure that the unique field is read-only when the user's email address is already filled in the field.
By setting the unique field to read-only when the user's email address is already filled in the field, you are allowing the user to not update that field while still maintaining the uniqueness constraint.