ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66087
|
Thu Nov 27 11:36:53 2008 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.5-2130 | Re: Select -> Edit wipes dates |
Stefan Ritt wrote: |
This problem has been fixed in revision 2.7.5-2143. Please upgrade.
|
Yup, this works now - thanks a mil! |
66280
|
Thu Mar 26 17:09:47 2009 |
| Dinkel Markus | m.dinkel@mr-daten.de | Question | Windows | 2.7.5-2175 | Re: New column on main page |
Stefan Ritt wrote: |
Dinkel Markus wrote: |
This is Ok but in wich file can i add this tag? In the .cfg-file?
|
Yes, this goes into the elogd.cfg file. Just add a line like:
[logbook]
Comment = OS-Version<br><i>192.160.0.1</i>
Then you will get something like this:

|
Thanks, this is great.
By, Markus |
66380
|
Fri Jun 5 12:02:45 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.6-2191 | Re: Moving entry (and replies) from one log book to another |
Thanks Stefan, Downloading shortly and I'll let you know ;-)
> > Hi Stefan,
> >
> > When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> > the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> > cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> > your FAQ about marking of whole threads).
> >
> > In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> > ID number.
> >
> > Thanks,
> >
> > David Pilgram.
>
> I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the
> configuration. I have not tested this extensively, but I'm sure you will do it ;-) |
66432
|
Thu Jul 2 11:33:48 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.6-2226 | Re: Cancelling an Roption selection in Edit. |
> > Hi Stefan,
> >
> > I don't know if anyone else would be interested or need this...
> >
> > If you have an Roption, and it is not required (maybe...) or have a preset attribute, it is possible to make an
> > entry and have replies without any of the attributes in that Roption being selected.
> >
> > However, once an attribute in that Roption has been selected, it is not possible to go back (editing) to the
> > condition before one was selected on that entry (so far as I can tell).
> >
> > Is a way of cancelling all the possible attributes in an Roption practical? Would others want it? It is
> > possible with options, as there is a "please select" which can be used to cancel whichever attribute in the
> > option that has been selected.
> >
> > Regards, David
>
> The easiest to achieve this is to define another option. Assume you have the three options
>
> One, Two, Three
>
> and you want to "unselect" them. So just add a fourth option like
>
> Unspecified, One, Two, Three
>
> so if you do not want any of the "One, Two, Three", just click on "Unspecified" and you get what you want.
This is sort of what I do now, I just wondered if there was a way of clearing that would leave the field completely
blank in the YYMMDDa.log file.
Thanks. |
66482
|
Wed Jul 29 13:23:41 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Odd problem (bug?) with certain attribute |
T. Ribbrock wrote: |
Very nice, thank you! Given that I also still have to test the fix you made for the crash problem with "shared" logbooks (I assume it's also present in 2244), I'll upgrade and report back (probably tomorrow).
|
2244 is now running, and indeed, the "Size" attribute works now. Thank you!  |
66483
|
Wed Jul 29 14:48:34 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good!  |
66523
|
Wed Sep 2 09:39:20 2009 |
| james Goedsir | james.goedsir@stratosglobal.com | Question | Windows | 2.7.7 | Re: Time Display Format |
james Goedsir wrote: |
My Time field is displayed i a 12 Hour format I would like to change it to 24 Hours, can someone advised how it can be done
|
Sorted no problem |
66543
|
Mon Sep 14 13:04:57 2009 |
| Gillian Sabberton | elog@gks.thamespower.com | Other | Other | ? | Re: Elog stopped working |
Gillian Sabberton wrote: |
Stefan Ritt wrote: |
Gillian Sabberton wrote: |
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem...
|
It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.
|
Have fixed this by removing the last added user from the Passwd file. |