discourse/app
Ted Johansson 06131bd4fd
FIX: Don't require fields required on sign-up when updating fields (#27888)
### What is the problem?

We have recently added a new option to add user fields required for existing users. This is in contrast to requiring fields only on sign-up.

This revealed an existing problem. Consider the following:

1. User A signs up.
2. Admin adds a new user field required on sign-up. (Should not apply to User A since they already signed up.)
3. User A tries to update their profile.

**Expected behaviour:**

No problem.

**Actual behaviour:**

User A receives an error saying they didn't fill up all required fields.

### How does this fix it?

When updating profile, we only check that required fields that are "for all users" are filled. Additionally, we check that fields that were required on sign-up and have previously been filled are not blanked out.
2024-07-15 09:56:20 +10:00
..
assets Revert "FEATURE: custom flag can require additional message (#27706)" (#27906) 2024-07-15 09:45:57 +10:00
controllers FIX: Don't require fields required on sign-up when updating fields (#27888) 2024-07-15 09:56:20 +10:00
helpers DEV: update base url links to respect subfolder installs (#27740) 2024-07-09 12:42:38 +04:00
jobs FEATURE: Add Mechanism to redeliver all failed webhook events (#27609) 2024-07-08 15:43:16 -05:00
mailers FIX: correctly compute the window for email summaries 2024-05-27 22:33:51 +02:00
models Revert "FEATURE: custom flag can require additional message (#27706)" (#27906) 2024-07-15 09:45:57 +10:00
serializers Revert "FEATURE: custom flag can require additional message (#27706)" (#27906) 2024-07-15 09:45:57 +10:00
services Revert "FEATURE: custom flag can require additional message (#27706)" (#27906) 2024-07-15 09:45:57 +10:00
views DEV: Upgrade the MessageFormat library (JS) 2024-07-10 09:51:25 +02:00