Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 38 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject Text Attachments
  1732   Tue Feb 28 11:26:22 2006 Reply Alex Halex@synergie-inf.comCommentWindows2.6.1-1668Re: MOptions problem ?> Hi Holger,

> > Which ELOG version do you use?
  
  1733   Tue Feb 28 12:08:42 2006 Cool Alex Halex@synergie-inf.comInfoWindows2.6.1-1668[SOLVED] Re: MOptions problem ?Yop,
I think I found the solution! I was in fact
a [B]conditions[/B] conflict!
 gotcha.gif 
  1734   Wed Mar 1 07:48:11 2006 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.6.1-1668[SOLVED] Re: MOptions problem ?[quote="Alex H"]It seems that the condition
ID must be unique across the whole elogd.cfg.[/quote]
  
  1735   Wed Mar 1 07:55:42 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-1653Re: list view mode remembert - Bug?> As default http://<hostname>/<LOGBOOK> shows
the Summary View.
> Clicking in "Full" changes the URL to http://<hostname>/<LOGBOOK>/?mode=full.
  
  1736   Wed Mar 1 10:30:51 2006 Reply Stefan Rittstefan.ritt@psi.chRequestWindowsV2.6.1-165Re: How to setup Change attributes in detail view/edit mode ?I implemented a "Hide attributes = ..." option,
with which you can do what you requested,
but unfortunately I'm
  
  1738   Wed Mar 1 12:27:36 2006 Idea Holger Mundhahsholger.mundhahs@vtg-rail.comQuestionWindows2.6.1-1653[SOLVED] Re: list view mode remembert - Bug?> > As default http://<hostname>/<LOGBOOK>
shows the Summary View.
> > Clicking in "Full" changes the URL to
  
  1782   Mon Apr 3 10:32:45 2006 Question Holger Mundhahsholger.mundhahs@vtg-rail.comQuestionWindows2.6.1-1681Change in encoding close entryMaybe it is a wrong configuration, because
in this forum it works well.
If I change the encoding in the logbook entry
  
  1783   Mon Apr 3 10:35:37 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.1-1681Re: Change in encoding close entry> Maybe it is a wrong configuration, because
in this forum it works well.
> If I change the encoding in the logbook
  
ELOG V3.1.5-3fb85fa6