Imagefield "Replace" not working from user/#/edit/profile, works from Profile Node [#366340]

Here's a strange one. On the site I'm working on, I'm using Imagefield with Content Profile to replace the built-in user photos. This has been all well and good and works great. But during testing, we have found that you can not replace the photos, when you access the profile vie user/#/edit/profile (Or whatever it would be if you clicked on the content profile tab when editing your account). Imagefield goes through all the motions, it looks like the image has been replaced; but when you click save, nothing changes- the image is not replaced or altered. This would be an imagefield bug if not for the fact that if you go directly to the profile node, (node/# for the user's profile) and replace the photo, it works perfectly. I have to look at what has been themed and how; none of the other information seems limited by this.

Comments

Comment #1

relaxatorium commented 13 February 2009 at 20:09

I am having this exact same problem, but with simple content text fields. Any progress on this issue?

Comment #2

relaxatorium commented 13 February 2009 at 20:49

A bit more useful information on this problem, as I investigate it further.

The node/#/edit form (which works) has submit buttons with code around them like so:

<input type="submit" name="op" id="edit-submit" value="Save"  class="form-submit" />
<input type="submit" name="op" id="edit-preview" value="Preview"  class="form-submit" />
<input type="submit" name="op" id="edit-delete" value="Delete"  class="form-submit" />
</div>

</div></form>

The user/#/edit/contentprofile form (which is the buggy one) looks like this around the buttons:

</div></form>
<input type="hidden" name="form_build_id" id="form-eeb409d6e750b7af967c8344525ca948" value="form-eeb409d6e750b7af967c8344525ca948"  />
<input type="hidden" name="form_token" id="edit-user-profile-form-form-token" value="c3a3eb12239ddae34ff298c7fdb2c0d9"  />

<input type="hidden" name="form_id" id="edit-user-profile-form" value="user_profile_form"  />
<input type="submit" name="op" id="edit-submit" value="Save"  class="form-submit" />
<input type="submit" name="op" id="edit-delete" value="Delete"  class="form-submit" />

</div></form>

The form builder for the second form seems to be inserting an extra

tag before the submit buttons are generated, which I suspect might be causing the bad behavior. I'll keep examining the module to see where this might be occurring, but if someone with actual experience in Drupal form building/module development could look at it, that would be even better.