ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 706 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6453 Entries

Goto page Previous 1, 2, 3 ... 705, 706, 707 ... 805, 806, 807 Next

Fri Oct 11 16:18:05 2013

Re: Navigation previous and next button don't work

Hung Dao wrote:

Stefan Ritt wrote:

Hung Dao wrote:

I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox.

Have you tried on this forum?

I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.

The data format has nothing to do with the functionality of browsing buttons. Except if you have an empty logbook, or a logbook with just one entry, then of course going forwared and backward will not make any sense.

67581

Fri Oct 11 19:20:22 2013

Re: Navigation previous and next button don't work

Stefan Ritt wrote:

Hung Dao wrote:

Stefan Ritt wrote:

Hung Dao wrote:

Have you tried on this forum?

I have a group includes more than one logbooks. One has about 1600 entries and another new one has 5 entries. I have tried them both. When I retested with v2.6.5, the buttons are still functional. This problem also exists on Firefox plus giving me a message "This is the first entry" "This is the last entry" when I clicked a previous button and next button respectively. I need to use v2.9.2 since it has many improvements

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.

- 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

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

67602

Tue Nov 5 23:21:52 2013

Compilation failure on Mac OSX 10.9

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

$ make

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -DHAVE_SSL -w -c -o crypt.o src/crypt.c

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -DHAVE_SSL -o elog src/elog.c crypt.o -lssl

src/elog.c:125:8: error: expected parameter declarator

size_t strlcpy(char *dst, const char *src, size_t size)

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

# define _USE_FORTIFY_LEVEL 2

src/elog.c:125:8: error: expected ')'

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

# define _USE_FORTIFY_LEVEL 2

src/elog.c:125:8: note: to match this '('

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

67603

Wed Nov 6 09:04:32 2013

Re: Compilation failure on Mac OSX 10.9

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan

67605

Thu Nov 7 02:18:17 2013

Re: Compilation failure on Mac OSX 10.9

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

Best regards,
Stefan

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.

I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!

Goto page Previous 1, 2, 3 ... 705, 706, 707 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6