ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 233 of 806

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 232, 233, 234 ... 804, 805, 806 Next

Thu Oct 19 12:42:42 2006

deletoille

xavier.deletoille@synchrotron-soleil.fr

Bug report

Linux | Windows

2.6.2-1723

Re: Date format in Threaded display

Stefan Ritt wrote:

deletoille wrote:

I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available?

Since you checked "Linux" in the "OS" of this entry, I was under the assumption that you were able to compile elog from the Subversion repository (http://savannah.psi.ch/websvn/filedetails.php?repname=elog&path=%2Ftrunk%2Fsrc%2Felogd.c).

If you need the Windows executable, I made http://midas/elog/download/windows/elog262-6.exe for you.

IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS A LOT

627

Wed Jul 28 21:34:35 2004

Re: 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

Steve Jones

steve.jones@freescale.com

Bug report

All

2.5.3

Re: 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

Re: 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

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

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

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

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"?>

<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?

Goto page Previous 1, 2, 3 ... 232, 233, 234 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6