ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 455 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6459 Entries

Goto page Previous 1, 2, 3 ... 454, 455, 456 ... 806, 807, 808 Next

Thu Jan 19 20:53:01 2006

Re: In version 2.6 the themes do not work right on Windows.

Mark Coudriet wrote:

But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help! Big grin

Japp. I switched back to relative links for CSS again, seems to give less trouble. Pleased

67572

Wed Oct 9 09:19:54 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Importing XML/CSV

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

67582

Sun Oct 13 16:32:05 2013

Re: Importing XML/CSV

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.

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

Attachment 1: umowy.cfg

[UMOWY]
Time format = %d %b %y - %H:%M
Date format = %d %b %y
Display mode = summary
Comment = Umowy
Menu commands = List, New, Edit, Reply, Delete, Duplicate, Find, Config, Logout, Help, Import
List Menu commands = List, New, Select, Find, Config, Logout, Help, Import


Attributes = Data dekretacji, Numer rejestru, Numer umowy, Nazwa dokumentu, Przedmiot umowy, Kontrahent, Data zawarcia, Data konca, Dzial, Status, Aneksy, Opis
List display = Data dekretacji, Numer rejestru, Numer umowy, Nazwa dokumentu, Przedmiot umowy, Kontrahent, Data zawarcia, Data konca, Dzial, Status, Aneksy, Opis

Style STATUS Nieaktualna = background-color:#FFC0CB
Style STATUS Aktualna = background-color:lightgreen



Preserve IDs = 0
Preset Numer rejestru = XXX/%Y/###
Quick filter = Numer rejestru, Numer umowy

Extendable options = Author, Carrier
Options Status = Aktualna, Nieaktualna
Options Aneksy = boolean


Options Okres obowiazywania = 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
Options Dzial = DA, DOP, DP, DTL, DTL BZG, DTL GDN, DTL KTW, DTL POZ, DTL WAW, DTL WRO, L&F
Options Przedmiot umowy = Obsluga, Najem, Media, Leasing
 
Format Numer rejestru = 0, attribname, attribvalue, 10, 10
Format Numer umowy = 0, attribname, attribvalue, 10, 20
Format Opis = 0, attribname, attribvalue, 1000, 1000



Comment Aneksy = Jezeli sa to zaznacz: X


Type Date of change = datetime
Type Data zawarcia = date
Type Data konca = date
Type Data dekretacji = date

Thread display = $Carrier $Name of Doc $Version No $Date of change entered by $author on $Entry time

Page Title =  Umowy Logbook - $Subject
Preset Author = $long_name
Locked Attributes = Author

Restrict edit = 0
Subst on reply subject = Re: $Subject
Suppress Email to users = 1
Theme = digilog
CSS = digilog.css
Title image = <img style="width:91;height:21;border:0" src="digilog.png" alt="eLOG" title="eLOG">
Top text = <img src="aerocol-transparent.png" style="height:46;width:146;border=0" alt="AeroSoft Systems Inc." title="AeroSoft Systems Inc.">&nbsp;<span class="asiTitle">DigiLOG&trade; Electronic Event Log</span>
Allowed encoding = 1
Suppress default = 3
Suppress Email on edit = 3
Fonts = Verdana, Geneva, Arial, Helvetica, sans-serif
Show attachments = 0
Preview attachments = 0
Append on reply = \n\nAdded $date by $long_name\n\n
Preset on reply Author = $long_name
Preset on reply Number= $Number
Subst on edit Author = $long_name
Fixed Attributes Edit = Author
Allow Delete = admin
Show text = 1


Sort Attributes = Carrier, Name of Doc, Version No
Message comment = Tu prosze umieszczac informacje o ANEKSACH oraz informacje dodatkowe:
Reply comment = Please enter your reply here:
Attachment comment = Tu prosze dodac zalaczniki:
Use Lock = 0
Fix text = 0
Logout to main = 1
Resubmit default = 2
Expand default = 1
Reverse sort = 1


Suppress default = 3
Suppress execute default = 2
Suppress Email on edit = 3

67585

Wed Oct 16 16:53:55 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Importing XML/CSV

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.

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.

Cheers, Andreas

Attachment 1: elogd.cfg

[global]
port = 8080

[TestXmlImportOfDate]
Attributes = D
Type D = date

Attachment 2: imp.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Mon  07 Oct 2013 11:41:42 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D>20.10.2012</D>
		<TEXT>ABCD</TEXT>
	</ENTRY>
	<ENTRY>
		<MID>2</MID>
		<DATE>Mon  07 Oct 2013 11:41:43 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D></D>
		<TEXT>DEF</TEXT>
	</ENTRY>
</ELOG_LIST>

67589

Tue Oct 22 10:56:13 2013

Re: Importing XML/CSV

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.

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.

Cheers, Andreas

�

Hi Andreas, Thanks for the reply. The suggested approach is workable, so I'll use that one. Regards, Barend

67350

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

67356

Thu Oct 4 11:35:12 2012

Andreas Luedeke

andreas.luedeke@psi.ch

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

66875

Thu Aug 5 12:26:12 2010

Re: Important security update of ELOG

Stefan Ritt wrote:

Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

Stefan Ritt

I just realized that the command line elog utility did not yet use the new encryption. So automatic elog submissions using passwords are broken in version 2.8.0. I made an intermediate version 2.8.0-2 which fixes that. However you only need to update it if you use the elog utility and have problems with the 2.8.0 version.

Goto page Previous 1, 2, 3 ... 454, 455, 456 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6