Re: Duplicate entry suggestion, posted by Stefan Ritt on Tue Apr 1 08:01:02 2008
|
| 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. |
|
Re: Can u send me the configuration file for this logbook ?, posted by Stefan Ritt on Tue Apr 1 08:04:18 2008
|
| 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
|
|
Re: Duplicate entry suggestion, posted by Dennis Seitz on Tue Apr 1 20:31:26 2008
|
| 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.
|
|
Re: FCKeditor not active, posted by Alain Hugentobler on Wed Apr 2 01:27:20 2008
|
| 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... |
|
Re: FCKeditor not active, posted by Kevin O'Sullivan on Wed Apr 2 03:34:43 2008
|
| 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. |
|
Re: FCKeditor not active, posted by Stefan Ritt on Wed Apr 2 09:19:55 2008
|
| 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. |
|
Re: e-mail format, posted by Stefan Ritt on Thu Apr 3 08:37:27 2008
|
| Bill Qualls wrote: |
|
I "upgraded" from v2.6.? to v2.7.3. By "upgrade", I mean "copy all files to a different computer, then run the installer". e-mail messages received from my v2.6 instance look nice. The messages look like HTML tables with blue and green coloring. My v2.7 instance appears to send plain text. But, when I forward the v2.7 message, the nice HTML tables appear again. Is there an e-mail formatting setting that I need to change?
|
That has probably to do with the program with which you read your email. The coloring is done in a cascading style sheet, which the email program has to load from the elog server upon display. Most programs ask you if you like to "load images" for this email. This is a bit misleading since the style sheet is no image, but similarly loaded form an external source. I use Thunderbird, which remembers my decisions. So if I get an elog message from a certain email sender, and I click on "load images always from this sender", then it will show the colored background for each following entry. If the sender now is different (like if you use a different computer), this will be different and you have to load images once by clicking somewhere (mostly a bar above your email display). |
|
Re: how to set locale for date/time, posted by Stefan Ritt on Fri Apr 4 08:20:06 2008
|
| svrmarty wrote: |
|
it seems out systemlang is en_US,
#date
Thu Mar 27 14:11:59 CET 2008
and i want to change the local lang only for the elogd.
i tried it with .bash_profile in the elog homedir with
LANG=de_AT
export LANG
but it doesn't work.
how can i change it to get ?
#date
Don Mär 27 14:09:14 CET 2008
|
I investigated this and found that elogd itself does not use the locale properly, so I have to change the code. I will let you know when I fixed this problem. |
|