Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 684 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  68275   Thu Mar 3 14:51:55 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.2Re: Attribute Field Size Limited to 255 Characters

No. At least there is no simple method.

You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have a hard time finding the right one to increase.

Cheers, Andreas

Mike Bodine wrote:

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

 

  68277   Tue Mar 8 14:12:26 2016 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.1Re: Execute new|edit doesn't seem to work

Juergen Diefenbach wrote:

Andreas Luedeke wrote:
I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0

If that is the case then Stefan will know where to look Wink

Cheers
Andreas


Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!

In principle I could live with this as I don't think I need to have drafts enabled.

Cheers,
Jürgen


I would speculate that "Execute new" is not executed, when a draft is saved (as one would expect, since it's only a draft), but is neither executed when a draft is submitted (not as one would expect).
Good that you're fine for the moment.
If you could add a minimal configuration to reproduce the problem, then Stefan would have it easier to debug it.
  68288   Wed Mar 16 08:39:55 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsELOG V2.9.2-247Re: upgrade problem
Hi Tim,
starting with ELOG version 3 all entries are moved into sub-directories for each year.
If you move the files back from the sub-directories and restart elogd, then the entries should appear again in the logbook with ELOG 2.9.2.
 
I don't know how to solve your other problem. Maybe you should talk to someone locally who can administer your windows server?
Cheers, Andreas
 
Tim Schelfhout wrote:

Hello there,

After several years of great ELOG usage I decided to upgrade our ELOG server.  I am using it to keep 
a logbook of my students.

ELOG runs as a windows service but since I cannot access or change windows services (only have access to the
ELOG directory) I upgraded by installing the executable to my laptop then copying the new ELOG version over the server installation.  

Tried this first on my laptop going from V2.9.2-2475  to the last version 3.1.1 and this worked without a problem.

When I tried to reproduce this on the server  all the data is there but ELOG displays it as if no theme was installed. (using the default
by the way)  No colors, no formatting
... at first I thougt this was because the copy was not complete but a second try reproduced the same result???

Tried going back to the old version but then ALL data was gone (structure and all logbooks still there, but data in logbooks gone) ....
Used -v switch to debug and the logging displayed an MD5 hash mismatch, so the logbooks could not be opened.  A restore fixed this ....
I guess upgrading means changing the logbook structure?

Anyway does anyone have any idea why the upgrade loses formatting ??  Tips are welcome

 

  68292   Wed Mar 23 11:40:52 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionAllELOG V2.9.2-245Re: Width of text field

Did you try the options

  • Summary lines = x
  • Summary line length = x

as documented in https://midas.psi.ch/elog/config.html#flags ?

It works nicely with plain text entries; it has some difficulties with HTML, since it has to remove the formatting and that disturbs the line count.

Cheers Andreas

Edward Diehl wrote:

I use a elog which has a text field to show log entries:  https://classis01.roma1.infn.it/elog/calib/     In the "Summary" view there are only 3 lines of about 40 characters shown, so often the entry is cut off even though there is plenty of space in the text box for longer lines.   To see the full entry you must click on the ID number.   Is there any way to configure the Text box to show longer lines?   Thank you.

 

 

  68304   Wed Apr 27 14:07:52 2016 Question Andreas Luedekeandreas.luedeke@psi.chRequestAllV3.1.1How to enforce line breaks in plain text entries?
We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?
  68305   Wed Apr 27 14:15:19 2016 Reply Andreas Luedekeandreas.luedeke@psi.chRequestAllV3.1.1Re: How to enforce line breaks in plain text entries?
> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas
  68306   Wed Apr 27 14:36:42 2016 Reply Andreas Luedekeandreas.luedeke@psi.chRequestAllV3.1.1Re: How to enforce line breaks in plain text entries?
> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.
  68317   Fri May 6 22:30:56 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinuxV2.7.8-2278Re: Merge duplicate types

I'm not sure I understand your question correctly.

If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.

John Mund wrote:

Hello,

We have accumulated some duplicate 'types' in one of our logbooks.  Is it possible to merge them?

Thanks,

John

 

 

ELOG V3.1.5-3fb85fa6