user_save() should document problems with category 'account'

What more do you need?

That is about as much backtrace as I know how to get.

As far as I can tell the only modules that should be involved are Profile and User Terms. I don't recall seeing this before the current version of User_Terms and 6.17 were installed, but we also added our 13th profile field at the same time.. Everything seems to work, except the fieldset label.

I suspect it's something I did, but I need help finding it.

I have confirmed this is a core "bug" (although it may just be poor docs). It happens on at least 6.17 and 6.19. You should be able to reproduce it by saving profile data in the "account" category. That is the default category in user_save, which is how my site is propagating the profile values. If I go into the profile_fields table and change all the category values to anything else, this issue goes away. Or I can make it go away by changing function profile_form_profile, adding a check for "account':

  while ($field = db_fetch_object($result)) {
    $category = trim($field->category);
    if (!isset($fields[$category]) && $category != 'account') {
      $fields[$category] = array('#type' => 'fieldset', '#title' => check_plain($category), '#weight' => $weight++);
    }

Then the API documentation needs to clearly state that "account" is reserved, and not that it is for profile fields (which is what it says now). As a matter of fact, it kind of implies that you should use "account."

That is good enough. Unfortunately my PC crashed and I haven't dowloaded the API stuff to this company PC, so I can't do it myself.