Re: In version 2.6 the themes do not work right on Windows., posted by Mark Coudriet on Thu Jan 19 20:50:29 2006
|
| Stefan Ritt wrote: |
| Quote: | | The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">). |
So what is your problem? Can't you access http://localhost:8080/demo/default.css ?
If so, you could use an
URL = http://{your host}:8080/
option in your config file, where you replace {your host} with your real host name. |
No, because they would have to be in every logbook instead of coming out of the theme directory.
But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help!  |
Re: In version 2.6 the themes do not work right on Windows., posted by Stefan Ritt on Thu Jan 19 20:53:01 2006
|
| Mark Coudriet wrote: | | But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help! |
Japp. I switched back to relative links for CSS again, seems to give less trouble.  |
|
Re: Importing XML/CSV, posted by Andreas Luedeke on Wed Oct 9 09:19:54 2013
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Re: Importing XML/CSV, posted by Barend on Sun Oct 13 16:32:05 2013 
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend |
Re: Importing XML/CSV, posted by Andreas Luedeke on Wed Oct 16 16:53:55 2013
|
| Barend wrote: |
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend
|
Hi Barend,
I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
⇄
Detect language » English
Cheers, Andreas
⇄
Detect language » English
⇄
Detect language » English
|
|
Re: Importing XML/CSV, posted by Barend on Tue Oct 22 10:56:13 2013
|
| Andreas Luedeke wrote: |
| Barend wrote: |
|
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend
|
Hi Barend,
I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
⇄
Detect language » English
Cheers, Andreas
⇄
Detect language » English
⇄
Detect language » English
|
Hi Andreas,
Thanks for the reply. The suggested approach is workable, so I'll use that one.
Regards, Barend |
|
Re: Importing XML, posted by Stefan Ritt on Wed Oct 3 14:05:15 2012
|
| David Chastain wrote: |
|
I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).
Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck.
Any thoughts or ideas?
|
What happens if you just export as .CSV and then import that file again. Does that work?
If not, can you post your .CSV file here and I will have a look.
Stefan |
Re: Importing XML, posted by Andreas Luedeke on Thu Oct 4 11:35:12 2012
|
| David Chastain wrote: |
|
[...] Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. Any thoughts or ideas?
|
I've successfully imported a large amount of entries from old non-ELOG logbooks via XML.
The only problem that I did run into was the date format: ELOG is very restrictive on the imported format; it has to be either "MM/DD/YY(YY) (HH:MM:SS)" or "DD.MM.YY(YY) (HH:MM:SS)".
When you export entries ELOG honours the "Date format" that you've specified in your elogd.cfg, therefore you cannot import the exported file until you reformat the date in the file.
Andreas |