http://bugs.xaraya.com/show_bug.cgi?id=6342
Summary: wrong date behaviour in xaruserapi/format_datetime.php
Product: App - Modules
Version: Weekly Tarball
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3 - Standard
Component: IEvents
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10
(like Gecko) (Debian)
Build Identifier:
1) No startdate and enddate (both empty)
all_day='A' (i.e. All day) gives result: "all day" (should be something like
"No date set")
all_day='T' (i.e. Timed event) gives result: "starts" (should be something like
"No date set")
2) Empty startdate, enddate: 2009-03-01 21:30:00, (in both all_day='A' and
all_day='T') gives result: "to March 01, 2009" (should be something like no
date set, as I suppose event has to start one day)
3) Enddate smaller than startdate in more days range (startdate: 2009-03-06
22:30:00, enddate: 2009-01-01 22:30:00, in both all_day='A' and all_day='T')
gives result: "March 06, 2009 to January 01, 2009" (should be either "March 06,
2009 to TBC" or "March 06, 2009, End Date is smaller than Start Date")
4) Enddate smaller than startdate in one day range (startdate: 2009-01-01
22:30:00, enddate: 2009-01-01 02:30:00)
A: "January 01, 2009 all day" (should be "January 01, 2009" or "January 01,
2009, End Date is smaller than Start Date")
T: "January 01, 2009 10:30 PM to 2:30 AM" (duration 0 minutes) (should be
"January 01, 2009 10:30 PM" or "January 01, 2009 10:30 PM, 2009, End Date is
smaller than Start Date")
Btw: do we really want to allow creating events with no startdate set?
IMHO it should't be allowed to create 3) and 4)
Reproducible: Always
--
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.