[Patch] Custom fields with date=false still behave as if it were set to true

[C. G. Brown]

The following custom field entry will still display a date in Trac 0.11.7:

[ticket-custom]
test1=text
test1.date=false
test1.date_empty=false
test1.label=Testing
test1.value=

The workaround is to remove the date entry altogether but if someone were just doing a quick change of a field this could become an issue. For us it's a an issue, albeit a minor one, because we have our own custom field manager and it's easier to pass false than to hide the value.

I'll see if I can produce a patch.

[C. G. Brown]

Patch to fix text being treated as date unless field.date=true

[Ryan J Ollos]

I can confirm this behavior and that the patch resolves the issue. Doki, can I go ahead and commit the patch?

[Ryan J Ollos]

I'm going to go ahead and apply the patch and assume that Doki will be okay with it, based on previous discussion. Otherwise I'll probably never get back to doing it.

[Ryan J Ollos]

(In [10398]) Fixes #7793: When field.date = false, the field was still being treated as a datefield. Thanks to cgbrown for the patch.

[Ryan J Ollos]

The egg file I accidentally added in [10398] was removed in [10399].