built-in term form fields aren't handled

Hi @joachim,
When i used this module i found that after clicking on "Save and add similar" button in add taxonomy form, term get saved but the content of the previous term don't come auto filled when the form for next term get loaded again.
So as to fix this issue i provided the above patch.
Thanks And Regards
Sanchi

Hi @joachim,
1. $fields = field_info_instances('taxonomy_term', $vocabulary_name);
I have not used this because it returns empty array as field_info_instances() calls _field_info_collate_fields() which returns
... [instances] = array(
.... [taxonomy_term] => Array
(
[tags] => Array
(
)

) ...
i.e. don't go in any condition in field_info_instances().
2.I have not used process function bacause :
if (array_key_exists('#default_value', $element) && array_key_exists('#value', $element)) {
any process function call will not go in this condition as #value of a newly created element is always empty.

$matching_fake_form_element = drupal_array_get_nested_value($form_state['taxonomy_add_previous_previous_term_form'], $element['#array_parents']);
this will set $matching_fake_form_element as
Array
(
[#type] => textfield
[#title] => Name
[#default_value] =>
[#maxlength] => 255
[#required] => 1
[#weight] => -5
)
having #default_value as empty.

$element['#value'] = $matching_fake_form_element['#default_value'];
so this will set $element['#value'] to null.

Please find the new patch having no process function.
Thanks And Regards
Sanchi

1.

I have not used this because it returns empty array
I don't understand what you mean here.
field_info_instances() returns an array of fields. It's the correct way to get the list of fields for the current term.

explanation of how it all woks:
when the function taxonomy_add_previous_form_taxonomy_form_term_alter(&$form, &$form_state, $form_id) { calls field_info_instances('taxonomy_term', 'tag');

function field_info_instances($entity_type = NULL, $bundle_name = NULL) {
  $info = _field_info_collate_fields(); 
  /*Returns an array  like 
       ... [instances] = array(
         .... [taxonomy_term] => Array
             (
               [tags] => Array
               (
               )
            ) ... */
  if (!isset($entity_type)) {//$entity_type = 'tag' so will not enter in this condition.
    return $info['instances'];
  }
  if (!isset($bundle_name)) { //$bundle_name = 'taxonomy_term'  so will not enter in this condition also.
    return $info['instances'][$entity_type];
  }
  if (isset($info['instances'][$entity_type][$bundle_name])) {/* as seen above it is also not set so will not enter in this condition also.*/
    return $info['instances'][$entity_type][$bundle_name];
  }
  return array(); /*thus returns empty array but this functions works for other forms and can see by displaying the content of _field_info_collate_fields(). */
}

2.

> if (array_key_exists('#default_value', $element) && array_key_exists('#value', $element)) {
> any process function call will not go in this condition as #value of a newly created element is always empty.
That's fine. That's why I'm using array_key_exists() rather than !empty().

if (array_key_exists('#default_value', $element) && array_key_exists('#value', $element)) {
but there is no array corresponding to #value or #default_value, you can see this by displaying the content of $element.

Thanks for guiding me.

Yes ,it should be 'tags' its my mistake .

but that's because on my site I have no fields defined on the tags vocab. That's normal.

But drupal standard profile provides us default vocabulary "tags" having fields name,description, url, parent.
So now what we should do to get data through field_info_instances('taxonomy_term', 'tags') ??

@joachim,
Most of us use these default fields only with in the 'tags' vocabulary so your module should work with that also.
So finally is this patch worth it ??

@joachim,
No, i want same data for name, desc, url, parent i.e. all fields should come for the next term which user can change accordingly.
I think this is what your module desc says

This module adds an extra button to the form for adding a taxonomy term. Whereas saving a new term normally takes you to a blank form for adding another term, this extra button inserts the fields values from the first term.

Regards
Sanchi