Drupal 5.x Form API: #value vs. #default_value
26 Sep, 2007
This is probably well documented if you look in the right place, but having just spent a number of hours puzzling through it on my own (despite) having access to documentation, I think it bears reiteration:
If you use '#value' when declaring a form element, that value is what will be received after submission, even if applied to a textfield that gets changed by the user. (This makes sense when passing a value behind the scenes, as you would do with a '#value' form element)
Use '#default_value' if you want the end-user to be able to modify the value.
Popular
Recently Perused
- If you're attending #drupalcon and you happen to be a #freemason, how about a BoF and/or lodge visit? http://is.gd/byget #mason — 4 years 37 weeks ago
- RT @nicklewisatx: I think I speak for all of #drupalcon when I ask @dries to announce that #drupal is declaring war on volcanoes — 4 years 37 weeks ago
- If science had been able to harness the power of Jack Webb's hatred for hippies, we could have stopped using oil decades ago. #fb — 4 years 37 weeks ago
- The #Drupal blueprint module adds its own JS which may break various ajax form submission modules. http://is.gd/bx5YE — 4 years 37 weeks ago
- Remember, kids: Check your #drupal module weights when your hook_form_alter() seems not to be working. — 4 years 37 weeks ago