Project

General

Profile

Actions
Copy link

Bug #53821

closed

Error with date/datetime fields and null evaluation

Added by Alexander Stehlik about 11 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
7 LTS
Start date:
2013-11-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I just stumbled upon this (maybe it is a TYPO3 bug, than this issue can be closed):

When you use eval='null' together with date or time it is important, that the date / time is added after null:

eval='null,time'

If you add null at the end the fields will not be displayed as date / time but as integer values.

Actions
Copy link
 #1

Updated by Francois Suter over 10 years ago

  • Tracker changed from Task to Bug
  • Project changed from 1369 to TYPO3 Core

Sorry for reacting belatedly, this was lost among other documentation issues. In my opinion this is a Core bug as there has never been any notion of precedence among the possible values of the "eval" property.

Actions
Copy link
 #2

Updated by Francois Suter over 10 years ago

  • Category set to Backend User Interface
  • Target version set to next-patchlevel
  • Is Regression set to No
  • TYPO3 Version set to 6.2
Actions
Copy link
 #3

Updated by Francois Suter over 10 years ago

  • Subject changed from Improve documentation for input eval null to Error with date/datetime fields and null evaluation
Actions
Copy link
 #4

Updated by Mathias Schreiber almost 10 years ago

  • Target version changed from next-patchlevel to 7.4 (Backend)
Actions
Copy link
 #5

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions
Copy link
 #6

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions
Copy link
 #7

Updated by Stefan Neufeind about 9 years ago

I could reproduce this on the current 6.2-branch, but not in 7-master (roughly 7.5.0 at this moment). Can somebody confirm it only affects 6.2 then?

Actions
Copy link
 #8

Updated by Frank Nägler about 9 years ago

  • Status changed from New to Needs Feedback
Actions
Copy link
 #9

Updated by Alexander Stehlik almost 9 years ago

Finally had the time to do some testing. I could not reproduce the issue any more in any current version (6.2, 7.6).

I nobody objects, issue can be closed :)

Actions
Copy link
 #10

Updated by Riccardo De Contardi almost 9 years ago

  • Status changed from Needs Feedback to Closed

Closed on request of the reporter.

Thank you very much for your time and investigations.

Actions
Copy link

Also available in: Atom PDF