Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 230 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6363 Entries 
Goto page Previous  1, 2, 3 ... 229, 230, 231 ... 794, 795, 796   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectup
  627   Wed Jul 28 21:34:35 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.3Re: Date format problem in "Thread display = "
> I get the following in my THREADED logbook view:
> 
> "Adding new services, planned for 1090519200. Last revised: Thu Jul 15
> 18:03:52 2004"

That should be fixed by the current version. Please update.
  634   Wed Jul 28 22:32:39 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: Date format problem in "Thread display = "
> > I get the following in my THREADED logbook view:
> > 
> > "Adding new services, planned for 1090519200. Last revised: Thu Jul 15
> > 18:03:52 2004"
> 
> That should be fixed by the current version. Please update.

Thanks!
  1581   Tue Jan 10 19:30:09 2006 Reply David Brodydbrody@echo-inc.comQuestion 2.5.8-2Re: Date imports from CSV incorrectly

David Brody wrote:
When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969

Here are the parameters I am using for dates:

Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y

Preset Status Date = $date


Thanks!

DB


Never mind. I figured it out!
  1297   Fri Jul 22 08:56:20 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.5.?Re: Date in CSV and XML in UNIX time

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.
  1310   Mon Jul 25 19:15:33 2005 Reply PJ Meyerpjm@pjmeyer.orgQuestionWindows2.5.?Re: Date in CSV and XML in UNIX time

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?
  1312   Mon Jul 25 20:20:18 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.5.?Re: Date in CSV and XML in UNIX time

PJ Meyer wrote:

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?


I just tried again myself. Put following into elgod.cfg:

[demo]
Attributes = Author, Category, Arrival
Type Arrival = Date


type in one entry, did a XML extract, and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Fri Jul 22 22:50:34 2005</DATE>
		<Author>sr</Author>
		<Category>Problem</Category>
		<Arrival>7/25/2005</Arrival>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

where the date looks ok. So what do you do differently?
  1316   Mon Jul 25 22:27:06 2005 Reply PJ Meyerpjm@pjmeyer.orgQuestionWindows2.5.?Re: Date in CSV and XML in UNIX time

Stefan Ritt wrote:

PJ Meyer wrote:

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?


I just tried again myself. Put following into elgod.cfg:

[demo]
Attributes = Author, Category, Arrival
Type Arrival = Date


type in one entry, did a XML extract, and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Fri Jul 22 22:50:34 2005</DATE>
		<Author>sr</Author>
		<Category>Problem</Category>
		<Arrival>7/25/2005</Arrival>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

where the date looks ok. So what do you do differently?



Not sure where we differ....

My cfg:
Attributes = System, Requestor, Title, Priority, Date Needed, Type, Also Notify, Subsystem, Status, Work Order, Assigned To, Team Lead, Percent Complete, Estimated Hrs, Actual Hrs, Date Added, Expected Delivery, Date Completed, Notifications, Completed
Options Priority = A-Emergency{p1}, B-Critical{p2}, C-High{p3}, D-Medium{p4}, E-Low{p5}
Preset Priority = D-Medium
Type Date Needed = Date

XML Extract:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>

<ENTRY>
<MID>585</MID>
<DATE>Wed Jun 22 08:29:58 2005</DATE>
<System>SDWIS</System>
<Requestor>Other...</Requestor>
<Title>EDI rejects report to George WAUN</Title>
<Priority>B-Critical</Priority>
<Date_Needed>1119384000</Date_Needed>


Q: could it be the spaces in Attribute name????
Or the differences between Linux and Windows ports?
  1319   Tue Jul 26 09:25:40 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.5.?Re: Date in CSV and XML in UNIX time

PJ Meyer wrote:
Q: could it be the spaces in Attribute name????
Or the differences between Linux and Windows ports?


I tried following elogd.cfg:
[global]
port = 8080

[demo]
Attributes = System, Requestor, Title, Priority, Date Needed, Type, Also Notify, Subsystem, Status, Work Order, Assigned To, Team Lead, Percent Complete, Estimated Hrs, Actual Hrs, Date Added, Expected Delivery, Date Completed, Notifications, Completed
Options Priority = A-Emergency{p1}, B-Critical{p2}, C-High{p3}, D-Medium{p4}, E-Low{p5}
Preset Priority = D-Medium
Type Date Needed = Date

and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>2</MID>
		<DATE>Tue Jul 26 09:10:33 2005</DATE>
		<System>s</System>
		<Requestor>r</Requestor>
		<Title>t</Title>
		<Priority>D-Medium</Priority>
		<Date_Needed>07/26/05</Date_Needed>
		<Type></Type>
		<Also_Notify></Also_Notify>
		<Subsystem></Subsystem>
		<Status></Status>
		<Work_Order></Work_Order>
		<Assigned_To></Assigned_To>
		<Team_Lead></Team_Lead>
		<Percent_Complete></Percent_Complete>
		<Estimated_Hrs></Estimated_Hrs>
		<Actual_Hrs></Actual_Hrs>
		<Date_Added></Date_Added>
		<Expected_Delivery></Expected_Delivery>
		<Date_Completed></Date_Completed>
		<Notifications></Notifications>
		<Completed></Completed>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

So I have the blank in the attribute, and I tried it both under windows and linux. I looked again at the code, and am pretty sure you run an old version. So I made a 2.6.0beta3 windows binaries, with which you could try it again.
Goto page Previous  1, 2, 3 ... 229, 230, 231 ... 794, 795, 796   Next  
ELOG V3.1.5-2eba886