Trying to CHANGE/UPDATE a Birth Date with the DATE feature within the USER PROFILE. It is NOT saving correctly. Also it seems that after posting info and saving it in other PROFILE areas and then trying to edit this info, it does NOT save the changes, keeps all the ORIGINAL data. ???
Comments
Comment #1
maptheway commentedI received three calls today from different clients with 4.5rc installed. Their members are NOT able to EDIT profiles. Can someone please grab this one to fix? Thanks.
Comment #2
dries commentedI can't reproduce this problem. Sorry. We can't fix something we can't reproduce.
What fields or field types can't be saved? Does other profile data get saved?
Comment #3
maptheway commentedDries,
You should now have all the examples for this edit not saving bug. Thanks very very much.
Comment #4
dries commentedI can see the problem on your site, but so far, I failed to reproduce it on my local setup. Are you using a recent Drupal version?
Comment #5
dries commentedThe generated XHTML code of your profile forms is incorrect. This is due to invalide XHTML code in the profile field descriptions, provided through the administration interface. I think that's causing the problem.
Comment #6
dries commentedI'm pretty sure the problem is caused by faulty HTML code in the profile field description. If it is not, please reopen this bug report.
Comment #7
maptheway commentedTurning off the html editor for the profiles section admin>users>configure>profiles and cleaning up the html mess left in each profile field did the trick.
The moral of the story: HTML editor can NOT currently be utilized inside the profile area. If it's showing up turn it OFF admin>settings>HTMLarea>textareas and uncheck all the status checks for stuff like admin/user/configure/profile etc.
Hope this helps.
Comment #8
boris mann commentedI've changed this back to active. Shouldn't it be considered a bug if HTML (regardless if used with HTMLArea or not) causes profile to break?
Fix should be to filter out "bad" HTML from the description.
Comment #9
robertdouglass commentedThis last comment is addressed in a new issue http://drupal.org/node/11528, which I will submit a patch for shortly.
Comment #10
drumm