Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 226 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66812   Fri May 7 15:35:12 2010 Reply ch huethuet@arronax-nantes.frBug reportWindowsV2.7.8-229Re: cell style bug?

Stefan Ritt wrote:

ch huet wrote:

hello

i've tried to change the color of a cell with "cell style"

it doesn't works

by removiving "cell" in the line ,just to get "style" the color of all cell of the row change (so it works for that...)

regards

As written here: https://midas.psi.ch/elogs/Forum/66807 you need to upgrade to version 2.7.8-5 of ELOG to get this functionality. 

 You're right my verssion was the previous one

  68334   Tue Jun 14 14:33:40 2016 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.1Re: cannot use "use email heading"

The setting

Use Email Heading

is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use

Email encoding = 1

and you get it.

/Stefan

utomoadji wisnubroto wrote:

Hello,

i have config file elogd.cfg like below:

[Tom Yaht]

Theme = default

;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook


;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2

Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to

Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager

;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated

The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading  above.

Could anybody help me.

Thank you

 

  68338   Wed Jun 15 02:42:53 2016 Reply utomoadji wisnubrotoutomoadji_w@yahoo.com.sgQuestionWindows3.1.1Re: cannot use "use email heading"

Hi Stefan,

Thanks for your reply, i got it now.

Thank you

Stefan Ritt wrote:

The setting

Use Email Heading

is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use

Email encoding = 1

and you get it.

/Stefan

utomoadji wisnubroto wrote:

Hello,

i have config file elogd.cfg like below:

[Tom Yaht]

Theme = default

;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook


;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2

Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to

Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager

;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated

The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading  above.

Could anybody help me.

Thank you

 

 

  66833   Tue Jun 1 13:17:18 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.7.8Re: cannot start elog

harley wrote:

I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago.  It's a wonderful thing to have.

I acquired another system running 10.6 to dedicate to the elog app.  I downloaded 2.7.8  and performed the following steps:

extract tarball in the desired directory

run

tar -xzvf elog-x.x.x.tar

 

switch to the new elog-x.x.x directory edit Makefile and elogd.cfg files as needed

to create executables

run

make


to create directories & files

run

make install

When I try to execute elog as a daemon:

 

elogd -c ~vulcanstaff/ELOG-Workspace/elog/elogd.cfg -D

I get the following message:

-bash: elogd: command not found

I'm not understanding why elogd cannot be found.  The same message occurs when I try to test the installation with elogd -p 8080 from the sbin directory where elogd is installed.
 
I'm using the same Makefile and elogd.cfg files that work on the old system.  My elogd and elogd.cfg files appear to be in the correct directories indicated in the Makefile:
 
#############################################################

#
# Directories for installation, modify if needed
#

ifndef PREFIX
PREFIX     = ~vulcanstaff/ELOG-Workspace
endif

ifndef MANDIR
MANDIR     = $(ROOT)$(PREFIX)/man
endif

ELOGDIR    = $(ROOT)$(PREFIX)/elog
DESTDIR    = $(ROOT)$(PREFIX)/bin
SDESTDIR   = $(ROOT)$(PREFIX)/sbin
RCDIR      = $(ROOT)$(PREFIX)/etc/rc.d/init.d

# flag for SSL support
USE_SSL    = 1

# flag for crypt() support
USE_CRYPT  =

#############################################################
 
Again, this works on the old system.  Perhaps I've looked at it for too long, but I can't figure out what's going on.  Assistance is greatly appreciated.
 
-harley

 

Some Linux systems don't have the current directory (".") in the search path, so you have to start it with

./elogd -c ....

or explicitly with

/usr/sbin/elogd -c ...

 

  67569   Mon Oct 7 10:12:31 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6Re: cannot add new logbooks to any of my logbook groups

Paraic Fahey wrote:

Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.

I have, up until recently been able to add new logbooks.

Can anybody help me on this.

Paraic Fahey

Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.

/Stefan 

  67570   Mon Oct 7 10:33:32 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindows2.7.6Re: cannot add new logbooks to any of my logbook groups

Stefan Ritt wrote:

Paraic Fahey wrote:

Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.

I have, up until recently been able to add new logbooks.

Can anybody help me on this.

Paraic Fahey

Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.

/Stefan 

 I cannot answer for Windoze, BUT there is more to this if you use Linux.

(Sorry for re-entry, I spotted a cut-and-paste error from first time around)

If you want to make a new logbook in linux manually, you need to do the following:

0.  Stop the elogd daemon.

1.  Edit elogd.cfg as Stefan said.  This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook.  Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook.  While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface.  Once restarted, you can then edit the config for the new logbook in the usual way.

2.  Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.

3.  Give that subdirectory the correct ownership and permissions.

4.  Only then, start elogd again.

As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know).  I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).

David.

  67580   Fri Oct 11 16:47:58 2013 Reply Paraic Faheyparaic.fahey@pfizer.comQuestionWindows2.7.6Re: cannot add new logbooks to any of my logbook groups

David Pilgram wrote:

Stefan Ritt wrote:

Paraic Fahey wrote:

Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.

I have, up until recently been able to add new logbooks.

Can anybody help me on this.

Paraic Fahey

Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.

/Stefan 

 I cannot answer for Windoze, BUT there is more to this if you use Linux.

(Sorry for re-entry, I spotted a cut-and-paste error from first time around)

If you want to make a new logbook in linux manually, you need to do the following:

0.  Stop the elogd daemon.

1.  Edit elogd.cfg as Stefan said.  This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook.  Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook.  While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface.  Once restarted, you can then edit the config for the new logbook in the usual way.

2.  Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.

3.  Give that subdirectory the correct ownership and permissions.

4.  Only then, start elogd again.

As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know).  I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).

David.

 David, Stefan,

Thanks for your help. Directly editing the elog.cfd file worked.

Paraic

  66751   Fri Mar 12 11:26:27 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.8-2280Re: can one use a IOption field for conditional tests?

FX FRERE wrote:

Hi again,

I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:

IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK

{1} Show Attribute Edit = Attribute1, Attribute2

Thread Icon = Status

Attribute1 and 2 do not have any sense if the result was successful,

ELOG interprets the {1} and {2} as being part of the icon name!

thanks again for your help

FX

Conditions won't work for IOption attributes. You need an additional attribute like:

Attributes = Status, Subject, Icon
Options Status = OK{1}, Failed{2}
Ioptions Icon = icon1.gif, icon2.gif

{1}Preset icon = icon1.gif
{2}Preset icon = icon2.gif
 
ELOG V3.1.5-2eba886