Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 64 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  1758   Mon Mar 6 18:36:34 2006 Smile Steve Jonessteve.jones@freescale.comQuestionAll2.5.9[RESOLVED] eLog Version number as eLog attribute?

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:
When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement footer is specified?

Thanks!


I added that feature, but will not be able to commit it before the next weekend.



Quote:
Not a problem! Thanks



Steve Jones wrote:
Works as requested!!
  67657   Mon Jan 20 19:15:24 2014 Question Daniel Camporadcampora@cern.chRequestAll2.9.2[Not] Submit on pressing enter key

Hello community,

I have a feature request for the form of the ELOG.

For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.

Cheers, keep up the good work,

Daniel

  69889   Sat Aug 16 14:31:49 2025 Angy Harry Martinharrymartin772@gmail.comOtherLinux3.1.5[CLOSED] Re: show attributes directive does not work? -- It does, if you use show attributes edit

Well, it DOES work.... but only if you use the "Show Attributes Edit" directive.  "Show Attributes" is only for the single entry pages, whereas "Show Attributes Edit" is for the "entry pages."

I should have read the docs more carefully, sorry.  But isn't this a bit inconsistent with the way other directives work?  Usually one uses "<Directive>" for new entries, "<Directive Edit>" for editing existing entries, and "<Directive Reply>" for replies.  So I am guessing that "Show Attributes Edit" will be used for new and edit?

Harry Martin wrote:

Follows a very simple logbook definition:

[simple]
Comment = test show attributes directive
Attributes = a, b, c
Show Attributes = a

(Assume that all attributes are used farther down.  This is for illustration only.)   

To see what I see when I run this tiny elogd.cfg, see attachment.

"Show attributes" does not seem to be working because all of the attributes are shown, not just those specified in the directive.  Or do I misunderstand/forget something?

 

 

  69890   Sat Aug 16 22:19:03 2025 Reply Harry Martinharrymartin772@gmail.comOtherLinux3.1.5[CLOSED] Re: 3-level conditional not working

Closed.  This "problem" was due to the same lack of document eyesight as https://elog.psi.ch/elogs/Forum/69889.   Sorry for all the noise.  New eyeglasses are forthcoming...

Harry Martin wrote:

Tried a variant, this time for NEW entries (not EDIT), which I meant to do to begin with; sorry if that was confusing. 

[cond_test]
attributes = region, manufacturer, model

options region = american{us}, japanese{jp}, european{eu}
show attributes = region

{us} options manufacturer = ford, chrysler, gm
{jp} options manufacturer = toyota{toy}, nissan{nis}, mitsubishi{mit}
{eu} options manufacturer = audi, mercedes, bmw, volvo, fiat
{us} show attributes = region, manufacturer
{jp} show attributes = region, manufacturer
{eu} show attributes = region, manufacturer

{toy} options model = corolla, prius, miata
{nis} options model = sentra, murano
{mit} options model = starion, outlander, mirage
{toy,nis,mit} show attributes = region, manufacturer, model

 I'm not sure if my multi-character conditional names are allowed or not, but they do seem to work... somewhat.  Note that I even tried a couple different ways of specifying which attributes to show (single versus multiple OR conditionals).  The problem now is that all of the attributes are always shown, seeming to ignore the conditionals entirely.

Harry Martin wrote:

Not sure if this is a bug or not; if it is not, kindly reclassify the category.

Following is a small example of what I will dub a 3-level, conditional logbook:

[cond_test]
attributes = region, manufacturer, model

show attributes edit = region
options region = american{1}, japanese{2}, european{3}

{1} options manufacturer = ford, chrysler, gm
{2} options manufacturer = toyota{4}, nissan{5}, mitsubishi{6}
{3} options manufacturer = audi, mercedes, bmw, volvo, fiat
{1,2,3} show attributes edit = region, manufacturer
{4} options model = corolla, prius, miata
{5} options model = sentra, murano
{6} options model = starion, outlander, mirage
{4,5,6} show attributes edit = region, manufacturer, model

This example is hardly complete, but it is sufficient to demonstrate the issue I am running into.  This works until I select from the 2nd level (manufacturer); it won't display the dropdown for the model (I think my show attribute edit is supposed to display that).  Is there a restriction on how many levels of conditional I can have?  If there is, it would be disappointing because I am trying to do something similar to this example.

I hope there is something very simple I can do to correct this, or perhaps a completely different approach that accomplishes the same thing.  I'd like to stick with the multi-level selection process as I have done here.

I am running elog 3.1.5 on Devuan Chimaera (approx. Debian Bullseye, sans systemd) in a Virtualbox VM.

 

 

  69359   Fri Apr 30 07:27:31 2021 Entry Faithfaithlessangel85@gmail.comBug reportLinuxV3.1.2[Bug?] Admin restrict edit time

I would like to know, if the command "Admin restrict edit time = " does really work as intended.

In my case I have the following global configuration:

Admin user = <me>
Restrict edit = 1
Restrict edit time = 1
Admin restrict edit time = 10000

And every time, when I want to edit an entry (as admin), that is older than 1 hour, i get the following error message:

"Entry can only be edited 1 hours after creation"

 

  1208   Wed Jun 22 11:04:41 2005 Warning Emiliano GabrielliAlberT@SuperAlberT.itBug reportAll2.6.0beta2[BUG] show only new entries
the new link "show only new entries" is very useful but seems to still have some problems:

  • I can't find any simple way to return to the "every entries" display .. may be the link has to be switched to a checkbox to be actived or not
  • I found a way (at least)... following the "config" link, doing nothing and coming back restores the view .. this is a feature now, but when a less tricky mechanism will be implemented will become a bug Tongue


another entry for my wishlist:
writeing the above code I noticed that the elcode buttons are lacking of a "
  • " shortcut .. it will be very usefull Smile

    PS:
    Writeing the wish above I noticed that the [ *] is interpreted as an item also otside the LIST tag .. so .. or the LIST tag is optional, or the [ *] should not be interpreted outside of it ... it's another bug ? TongueP
  •   1210   Thu Jun 23 11:03:18 2005 Warning Emiliano GabrielliAlberT@SuperAlberT.it Linux2.6.0beta2[BUG] quick filter
    it seems that the select box of quick filters are showing also the "{n}" appended to the Attributes in order to obtain conditional Attributes ...

    see the snapshot attached
    Attachment 1: elog-calendar-test_1.jpg
    elog-calendar-test_1.jpg
      1223   Mon Jul 4 18:46:25 2005 Entry Emiliano GabrielliAlberT@SuperAlberT.itBug reportAllcvs[BUG] attach=1 and inline imgs
    There is a little difference in the way elog treats attachment's display in list and single message view...
    It has to be, but some beaviours can be seen as bugs:

    • this is a real bug (see attachment).. if a file is referred inside the text (as shown in elcode docs) it is correctly not shown when in single message view, but it remains visible both inline and as attachment in the full list view
    • it would be nice for the user having, as in the single message view, the possibility of show or hide a single or all the attachements of a single message ..
    Attachment 1: elog-showattach_bug.jpg
    elog-showattach_bug.jpg
    ELOG V3.1.5-3fb85fa6