Answers.Body: <p>I believe that you can get the options directly from the 'currentUser' entry, without referring to 'user' separately (they are likely the same thing in this case anyway):</p>
  
  <pre><code>&lt;label for="providerLanguages"&gt;What languages do you work with?&lt;/label&gt;
  {% for option in currentUser.providerLanguages.options %}
      &lt;input type="checkbox" id="providerLanguages" name="fields[providerLanguages][]"
      {% if option.selected %}checked{% endif %} value="{{ option.value }}"&gt;
          {{ option.label }}
      &lt;/input&gt;
  {% endfor %}
  </code></pre>
  
  <p>The value is also available as 'option.value' instead of 'option.selected'.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-11-20T23:53:22.540Z
Answers.Text: `user` is deprecated. `currentUser` is the way to go.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-11-20T23:59:55.307Z
Answers.Text: @Brad what will the variable be called when viewing or editing someone else's profile?
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-11-21T00:04:06.993Z
Answers.Text: Whatever you set it to? Pretty sure that was the original issue. `user` used to be global, but people were inadvertently overwriting it in their template code, so we changed the global to `currentUser`.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-11-20T23:35:07.680Z
Answers.LastActivityDate: 2014-11-20T23:35:07.680Z
Answers.UserDisplayName: Douglas McDonald
Body: <p>I'm trying to set up a front end user profile that will allow the user to use the multi-select field. When I update from the CP, the changes are reflected on the front end, but this isn't working when trying to update from the front end form.</p>
  
  <p>Is there anything I'm missing?</p>
  
  <pre><code>{% set languageOptionsIds = user.providerLanguages %}
  
  &lt;label for="providerLanguages"&gt;What languages do you work with?&lt;/label&gt;
  {% for option in currentUser.providerLanguages.options %}
      &lt;input type="checkbox" id="providerLanguages" name="fields[providerLanguages][]"
      {% if option.selected in languageOptionsIds %}checked{% endif %} value="{{ option.selected }}"&gt;{{ option.label }}
      &lt;/input&gt;
  {% endfor %}
  </code></pre>
  
Tags: <templating><users><form>
Title: Edit multi-select field from front end
ThreadText: # Edit multi-select field from front end
  
  (Asked by: username_0 on 2014-11-20)
  
  I'm trying to set up a front end user profile that will allow the user to use the multi-select field. When I update from the CP, the changes are reflected on the front end, but this isn't working when trying to update from the front end form.
  
  Is there anything I'm missing?
  
  ```
  {% set languageOptionsIds = user.providerLanguages %}
  
  <label for="providerLanguages">What languages do you work with?</label>
  {% for option in currentUser.providerLanguages.options %}
      <input type="checkbox" id="providerLanguages" name="fields[providerLanguages][]"
      {% if option.selected in languageOptionsIds %}checked{% endif %} value="{{ option.selected }}">{{ option.label }}
      </input>
  {% endfor %}
  
  ```
  
  **Tags:** templating, users, form
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-11-20. Score: 3 | Accepted answer
  
  I believe that you can get the options directly from the 'currentUser' entry, without referring to 'user' separately (they are likely the same thing in this case anyway):
  
  ```
  <label for="providerLanguages">What languages do you work with?</label>
  {% for option in currentUser.providerLanguages.options %}
      <input type="checkbox" id="providerLanguages" name="fields[providerLanguages][]"
      {% if option.selected %}checked{% endif %} value="{{ option.value }}">
          {{ option.label }}
      </input>
  {% endfor %}
  
  ```
  
  The value is also available as 'option.value' instead of 'option.selected'.
  
  > **Comments:**
  > **username_2**: `user` is deprecated. `currentUser` is the way to go.  
  > **username_1**: @username_2 what will the variable be called when viewing or editing someone else's profile?  
  > **username_2**: Whatever you set it to? Pretty sure that was the original issue. `user` used to be global, but people were inadvertently overwriting it in their template code, so we changed the global to `currentUser`.  
  
  ---
  
  