Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 718 of 806  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  66030   Thu Oct 30 21:14:32 2008 Reply Barendb.vandevrande@amtc2.comQuestionWindows2.7.5-2130Re: Standard login Screen - bottom text

Stefan Ritt wrote:

 

Barend wrote:

Hi Stefan.

I have been "playing" around with this great tool and found an interesting "issue" ...

I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".

When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.

When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.

How can I apply my own Bottom Text to the Standard Login Screen ?

Thanks & Regards, Barend
 

 

 By using the configuration option "Bottom Text Login = ..."

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

  66130   Mon Dec 29 17:27:13 2008 Reply Barendb.vandevrande@amtc2.comQuestionWindows2.7.5-2130Re: Standard login Screen - bottom text

Stefan Ritt wrote:

Barend wrote:

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

 That's strange. I just tried myself following configuration file:

[global]
port = 8080
Bottom text = 
Hello
Bottom text login =
Login Hello
Password file = passwd [demo1] Comment = General linux tips & tricks Attributes = Author, Type, Category, Subject Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Page Title = ELOG - $subject [demo2] Comment = General linux tips & tricks Attributes = Author, Type, Category, Subject

and everything works fine as can be seen from the login screen:

Capture.jpg

so can you check if above file works for you?

 Hi Stefan,

Hope you have enjoyed the Christmas week.

Sorry for the delay.... I have tested your configuration and it worked for me as well. 

In order to determine, which of my settings is causing the problem, I had to activate each individual entry "one by one" and check if the error re-occured. I finally identified following entry "Protect Selection page = 1"

The error also occurs if I change your configuration into:

[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd
Protect Selection page = 1

[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject

[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
 

Can you advise if I'm missing an entry in order for "Protect Selection page = 1" to work?

 

"Schönen Rutsch ins neue Jahr".

Regards, 

Barend

  67410   Wed Jan 2 14:04:41 2013 Question Barendoffice@amtc2.comQuestionWindows2.9.2Hide/Un-hide Commands based on Attribute Option value

Hi Stefan,

Happy New Year!

I ran several searches thru the forum but I could not detect a suitable entry on the following:

Is it possible to hide/un-hide the Commands, like "Edit", "Reply", "Duplicate", from the Menu based upon an Option of an Attribute?

E.g. Attributes = Status, .. | Options Status = Open, Closed

When Status = "Open"; the Menu Commands "Edit", "Reply" and "Duplicate" are available.

When Status = "Closed"; the Menu Commands "Edit", "Reply" and "Duplicate" are hidden/not available.

-or-

Can this only be accomplished using 2 Logbooks (Open / Closed) and move an entry from "Open" to "Closed" where the Logbook "Closed" is not using the Commands  "Edit", "Reply", "Duplicate".

 

Kind regards,

Barend

  67411   Wed Jan 2 15:38:19 2013 Question Barendoffice@amtc2.comQuestionWindows2.9Re-using IDs after move to another Logbook overwrite Entries

Hi Stefan,

I have observed following behavior when I move entries from one logbook to another:

  1. The first entry in "Open" get ID "1"
  2. When I move this Item to "Closed", it will keep ID "1" as I have used "Preserve IDs = 1"
  3. A new entry in "Open" gets ID "1" again
  4. When I move this item to "Closed" it will overwrite the previous ID "1" in "Closed"
  5. A new entry in "open" gets ID "1" again....

Every new entry in "Open" will get the next higher ID Number related to the highest available ID number/entry in "Open".

Upon "move to Closed", the previous entries in "Closed"will be overwritten.

Is there a way to prevent the usage of a previously used ID Number when entering a new ID?
I.e. If an entry with ID "1" has been used in "Open" and moved to "Closed", have the next entry in "Open" use ID "2"?

Kind regards,

Barend

  67428   Thu Jan 24 10:42:13 2013 Reply Barendoffice@amtc2.comQuestionWindows2.9Re: Re-using IDs after move to another Logbook overwrite Entries

Stefan Ritt wrote:

David Pilgram wrote:

Barend wrote:

Hi Stefan,

I have observed following behavior when I move entries from one logbook to another:

  1. The first entry in "Open" get ID "1"
  2. When I move this Item to "Closed", it will keep ID "1" as I have used "Preserve IDs = 1"
  3. A new entry in "Open" gets ID "1" again
  4. When I move this item to "Closed" it will overwrite the previous ID "1" in "Closed"
  5. A new entry in "open" gets ID "1" again....

Every new entry in "Open" will get the next higher ID Number related to the highest available ID number/entry in "Open".

Upon "move to Closed", the previous entries in "Closed"will be overwritten.

Is there a way to prevent the usage of a previously used ID Number when entering a new ID?
I.e. If an entry with ID "1" has been used in "Open" and moved to "Closed", have the next entry in "Open" use ID "2"?

Kind regards,

Barend

 Hi Barend,

The counting of entries, or even "tickets", only works within a particular logbook.  If you archive a set of entries to another [archive] logbook, the archived set disappears from view of the original logbook.  Should that entry, from logbook to archive, be the *latest* thread, then there is the danger of over-writing message ID, Ticket No and the like.

 

My policy to prevent the problem is to archive only threads that are say (depending upon use) a month after last entry..

 

 

I generally consider using the ID as ticket number a bad idea. The ID is the "primary key" (in terms of database language), and must be unique inside a logbook. So when moving entries between logbooks, there will be always problems.

Why don't you define an attribute "Ticket ID" and use that one? That won't change when you move the entry between logbooks:

Attributes =  Ticket ID, Subject, ...
Preset Ticket ID = ID-#####

 

 Hi All,

 

I have tried to use the "Ticket ID" approach and with each new entry this Ticket ID is indeed increased automatically...

But when the last Entry (with the highest Ticket ID i.e. ID-0009) is move to another Logbook, the Ticket ID in the next new entry will be "ID-0009" again (based upon the last previous entry "ID-0008").

So this appraoch will also re-produce duplicate Ticket IDs.

Is it possible to have the Ticket ID preset with value based upon the Date & Time of the entry? Instead of holding a Date/Time format, use a calculated numeric format?

This way, each new entry will have a truely unique Ticket ID.

Thanks & Regards, Barend 

  67571   Tue Oct 8 18:14:20 2013 Warning Barendoffice@amtc2.comBug reportWindows2.9.2Importing XML/CSV

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?

Attachment 1: import.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>
		<Data_dekretacji>01.10.2013</Data_dekretacji>
		<Numer_rejestru>XXX/2013/001</Numer_rejestru>
		<Numer_umowy>44/333/N/2012</Numer_umowy>
		<Nazwa_dokumentu>XXXXXXXXXXXXXXXX</Nazwa_dokumentu>
		<Przedmiot_umowy></Przedmiot_umowy>
		<Kontrahent>AAAAAAAA BBBBBBBBBB</Kontrahent>
		<Data_zawarcia>10.07.2012</Data_zawarcia>
		<Data_konca>10.07.2013</Data_konca>
		<Dzial></Dzial>
		<Status>Nieaktualna</Status>
		<Aneksy></Aneksy>
		<Opis></Opis>
		<Opis2></Opis2>
		<Opis3></Opis3>
	</ENTRY>
	<ENTRY>
		<MID>2</MID>
		<DATE>Mon  07 Oct 2013 11:41:42 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<Data_dekretacji>01.10.2013</Data_dekretacji>
		<Numer_rejestru>XXX/2013/002</Numer_rejestru>
		<Numer_umowy>33/330/N/2012</Numer_umowy>
		<Nazwa_dokumentu>CCCCCC DDDDDDDD</Nazwa_dokumentu>
		<Przedmiot_umowy></Przedmiot_umowy>
		<Kontrahent>XXXXXXXXXXXXXX</Kontrahent>
		<Data_zawarcia>01.06.2012</Data_zawarcia>
		<Data_konca></Data_konca>
		<Dzial></Dzial>
		<Status>Aktualna</Status>
		<Aneksy></Aneksy>
		<Opis></Opis>
		<Opis2></Opis2>
		<Opis3></Opis3>
	</ENTRY>
</ELOG_LIST>
  67582   Sun Oct 13 16:32:05 2013 Reply Barendoffice@amtc2.comBug reportWindows2.9.2Re: 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

  67583   Mon Oct 14 12:08:16 2013 Question Barendoffice@amtc2.comQuestionWindows2.9.2Error: Attribute <date> not supplied.

Stefan/Andreas,

When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."

The configuration file uses:

Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
 

The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.

As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.

But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.

 

Is this a bug -or- do I have to change the configuration?

 

Thanks & regards, Barend

ELOG V3.1.5-3fb85fa6