Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 223 of 796  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65795   Thu Mar 27 09:23:25 2008 Reply svrmartysvrmarty@gmx.netQuestionLinux 2.6.3+r17Re: change language

Stefan Ritt wrote:

svrmarty wrote:

i've installed the debian package on my system

there's only one config file, /etc/elog.conf

i've tried to change the language, in [global] with Language = german,

then restarting the daemon,  but it doesn't work.

please help me, where can i change the default(all) language and which settings should i do.

I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:

strace -r -o tmp.log -e trace=open /usr/local/elog/elogd

and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.

in the trace is only one config file

     0.000103 open("/etc/elog.conf", O_RDONLY) = 3
     0.000047 open("/etc/elog.conf", O_RDONLY) = 3

  65796   Thu Mar 27 09:30:03 2008 Reply svrmartysvrmarty@gmx.netQuestionLinux 2.6.3+r17Re: change language

svrmarty wrote:

Stefan Ritt wrote:

svrmarty wrote:

i've installed the debian package on my system

there's only one config file, /etc/elog.conf

i've tried to change the language, in [global] with Language = german,

then restarting the daemon,  but it doesn't work.

please help me, where can i change the default(all) language and which settings should i do.

I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:

strace -r -o tmp.log -e trace=open /usr/local/elog/elogd

and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.

in the trace is only one config file

     0.000103 open("/etc/elog.conf", O_RDONLY) = 3
     0.000047 open("/etc/elog.conf", O_RDONLY) = 3

 

there's a bug in the debian package

     0.000033 open("resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)
     0.000264 open("/usr/share/elog/resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)

it's searching for the files in the wrong directory.

i've solved it with

#/usr/share/elog$ ln -s . resources

 

  65800   Tue Apr 1 08:01:02 2008 Reply Stefan Rittstefan.ritt@psi.chRequestAll Re: Duplicate entry suggestion

Dennis Seitz wrote:

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.

  65801   Tue Apr 1 08:04:18 2008 Reply Stefan Rittstefan.ritt@psi.chRequestWindows Re: Can u send me the configuration file for this logbook ?

Franck C wrote:

Hi, I try to set up a logbook and i wanted to create something with icons (like this logbook) and it will be easier for me if i have ur config file

Thanks a lot

Franck

https://midas.psi.ch/elogs/Config+Examples/2

- Stefan

 

  65802   Tue Apr 1 20:31:26 2008 Reply Dennis Seitzdseitz@berkeley.eduRequestAll Re: Duplicate entry suggestion

 

Stefan Ritt wrote:

 

Dennis Seitz wrote:

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

 

I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.

 

Thanks, I was not aware of that - usually I have copied and pasted the entire path from my browser.

In any case, can you consider my request for possible future implementation? I think it's a useful function. For now, it's really no big deal to simply copy the url before selecting the Copy To: menu and then replacing the body text with the copied link. But I think it would be more useful to make this happen automatically, so I don't have to ask users to comply voluntarily.

Thank you.

 

  65805   Wed Apr 2 01:27:20 2008 Reply Alain HugentoblerAlain.Hugentobler@unige.chQuestionLinux2.7.3-2058Re: FCKeditor not active

Kevin O'Sullivan wrote:

I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?

Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)

A better solution is to modify the Makefile :

@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

which doesn't work on my Ubuntu 8.04; however changing to:

@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

does...

  65806   Wed Apr 2 03:34:43 2008 Reply Kevin O'Sullivankosok@stanford.eduQuestionLinux2.7.3-2058Re: FCKeditor not active

Alain Hugentobler wrote:

Kevin O'Sullivan wrote:

I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?

Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)

A better solution is to modify the Makefile :

@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

which doesn't work on my Ubuntu 8.04; however changing to:

@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

does...

That fixed it!

Thanks Alain.

  65807   Wed Apr 2 09:19:55 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.3-2058Re: FCKeditor not active

Alain Hugentobler wrote:

Kevin O'Sullivan wrote:

I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?

Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)

A better solution is to modify the Makefile :

@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

which doesn't work on my Ubuntu 8.04; however changing to:

@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/

does...

I didn't realize that the Ubuntu version of unzip does not support the -f flag. Anyhow it's not really necessary, so I removed it from the distribution. The fix will be contained in the next release.

ELOG V3.1.5-2eba886