Entered data is processed malformed and not being saved

Hi,
I had a look and it seems to work fine for me.
Which version of 'date' are you using?
What is your input format?

Hi boneless,

I'm using Date 5.x-1.8. admin/settings/date-time is configured to

* Short: 31 Mär 2008 - 12:31
* Medium: 31. März 2008 - 12:31
* Long: Montag, 31. März 2008 - 12:31

The created taxonomy field in admin/content/taxonomy_fields is formatted:

* Select List - or - Text Field (same error); when "Select list":
** Input format: Site default
** Select list: Year, Month, Date
** Granularity: Year, Month, Date
** Default Display: 31. März 2008 - 12:31
** Time zone handling: No time zone conversion

Display settings:
* Label: Inline
* Teaser: Standard - or- As Time Ago (same error, no matter what is configured here)
* Full: Standard

Have I missed something? Is there something else to sonsider?

Thank you for the quick reply!
-asb

hey,
I used exactly the same settings described above as well as the German translation and it does the trick here.
Can you please try and just use ONLY CCK, taxonomy fields and date on a clean Drupal 5.7 install?
I am pretty sure it must be something with another module or a setting, perhaps a server setting?
Does the error appear if date is used in a normal content type?
You can also send me an email on my contact form.

Hi,

the concept of Taxonomy Fields is such an great idea, and I'm still stunned by the sheer amount of possibilities it provides. However, there seem to be serious glitches in the modules stability. Most of what I try to accomplish, Taxonomy Fields won't let me do it. The above example was supposed to become a publishing date, attached to a term for a media typ (like a book or a magazine) which have a release date; that gave the above error.

Now I've tried to add some data to zoological terms in a vocabulary targeted to describe species. The vocabulary allows to select different species, and I'd like to add CCK fields which describe the species in more detail without creating a new content type. That's where Taxonomy Fields module should jump in; I'd like to add stuff like height, weight, etc. to certain term.

Again, Taxonomy Fields can be attached to terms of the vocabulary; however, most of the stuff I'm entering is *not* being saved. Example:

* Field: field_widerristhhe_rde (German umlauts seem to be automatically removed)
* Label: "Widerristhöhe ♀"
* Widget: Select list

* Text processing: Plain text
* Maximum length: 25

Allowed values list:

Display settings:

* Typ: Text
* Label: Inline
* Teaser: Default
* Full: Default

In edit view, the widget appears as wanted; if a choose a value, e.g. "55 cm (± 5 cm)", and save the node, nothing is displayed, neither in teaser view, nor in full view; if I edit the node again, the fields are empty. This I can repeat several times - the "Taxonomy Fields" modules always "forgets" the entered data.

On the other hand, I was able to create at least *one* Taxonomy Field (integer) where data is memorized and displayed by the module, so basically it seems to work.

Greetings, -asb

again, the given example works fine for me.
my guess: your are using the wrong field type.
are you using a 'integer' or 'decimal' field instead of a 'text' field? they will never save a value like '70 cm (± 5 cm)' as it is a text and not a number! please check your field type.
regarding the 'date' field i tried quite a few possibilities, it works fine for me. i can't do much more if i don't have more information.
have you tried ONLY CCK, taxonomy fields and date on a clean Drupal 5.7?

Hi,

> my guess: your are using the wrong field type.
> are you using a 'integer' or 'decimal' field instead of a 'text' field? they will never save a value like '70 cm (± 5 cm)' as it is a text
> and not a number! please check your field type.

From admin/content/taxonomy_fields:

If I edit a node with an attached date_text Taxonomy field, now I get this error:

> have you tried ONLY CCK, taxonomy fields and date on a clean Drupal 5.7?

No, sorry, I don't have such an installation on hand. But I tested Taxonomy Fields on different and separate Drupal installations, with similar results.

Is there anything else I could check?

Thanks & greetings, -asb