Re: Datepicker not showing, posted by Andreas Luedeke on Mon Dec 12 09:48:14 2016
|
Just last week I've downloaded the latest version of ELOG, compiled and installed it, and the date picker just works fine.
In my case it was an update of an existing installation. Can you provide a bit more information about your case: I guess it was a first time installation? Was is ELOG V3.1.2-754330e or a different GIT version?
Stefan, could you please add an attribute of type "datetime" and "date" to one of the demo logbooks? Currently there is non. Maybe to elog:Database? Then we can check if it is a client problem.
Cheers, Andreas
| Christine Quicot wrote: |
|
Hello users,
When I configure an attribute with "Type <attribute>= date", in the new entry form a clic on the calendar symbol does nothing.
Reading the source code I see it's trying to open a window named "cal.html" through javascript (function opencal) but this file doesn't exist anywhere in source elog files.
Thanks
|
|
|
Re: Datepicker not showing, posted by Stefan Ritt on Mon Dec 12 10:14:50 2016
|
I put one in https://midas.psi.ch/elogs/Database/?cmd=New
Could also be a pop-up blocker problem. Let's see.
Stefan
| Andreas Luedeke wrote: |
|
Just last week I've downloaded the latest version of ELOG, compiled and installed it, and the date picker just works fine.
In my case it was an update of an existing installation. Can you provide a bit more information about your case: I guess it was a first time installation? Was is ELOG V3.1.2-754330e or a different GIT version?
Stefan, could you please add an attribute of type "datetime" and "date" to one of the demo logbooks? Currently there is non. Maybe to elog:Database? Then we can check if it is a client problem.
Cheers, Andreas
| Christine Quicot wrote: |
|
Hello users,
When I configure an attribute with "Type <attribute>= date", in the new entry form a clic on the calendar symbol does nothing.
Reading the source code I see it's trying to open a window named "cal.html" through javascript (function opencal) but this file doesn't exist anywhere in source elog files.
Thanks
|
|
|
|
Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Fri Jul 22 08:56:20 2005
|
| 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. |
|
Re: Date in CSV and XML in UNIX time, posted by PJ Meyer on Mon Jul 25 19:15:33 2005
|
| 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? |
|
Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Mon Jul 25 20:20:18 2005
|
| 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? |
|
Re: Date in CSV and XML in UNIX time, posted by PJ Meyer on Mon Jul 25 22:27:06 2005
|
| 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? |
|
Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Tue Jul 26 09:25:40 2005
|
| 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. |
|
Re: Date imports from CSV incorrectly, posted by David Brody on Tue Jan 10 19:30:09 2006
|
| 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! |
|