| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69043
|
Wed Oct 16 11:06:34 2019 |
 | Moustafa Messed | moustafa.messed@cern.ch | Other | Linux | latest | ELOG Stop working with kerberos configuration | Dear All
i have this problem since i tried to install ELOG latest version while make Authetnetication Kerberos ELOG stop runing any idea or help please
|
|
69889
|
Sat Aug 16 14:31:49 2025 |
 | Harry Martin | harrymartin772@gmail.com | Other | Linux | 3.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 |
 | Harry Martin | harrymartin772@gmail.com | Other | Linux | 3.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.
|
|
|
|
44
|
Mon Jul 1 10:36:47 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Admin password | > I want to set up eLogs for a class w/out the need for passwords. But, at the
> same time, I don't want the students to change the config file. I tried
> setting up a global password, but am having some difficulty with the syntax
> I suppose I could remove the config command from the menu and edit the file
> using Pico, but that would require a better memory than I have...
>
> ******************
>
> usage: elogd [-p port] [-h hostname] [-D] [-c file] [-r pwd] [-w pwd] [-a
> pwd] [-l logbook]
>
> -p <port> TCP/IP port
> -h <hostname> TCP/IP hostname
> -D become a daemon
> -c <file> specify configuration file
> -v debugging output
> -r create/overwrite read password in config file
> -w create/overwrite write password in config file
> -a create/overwrite admin password in config file
> -l <logbook> specify logbook for -r and -w commands
>
> -k do not use keep-alive
>
> [root@eMonster elog]# elogd -a youtheman
>
> Must specify a lookbook via the -l parameter.
Nearly correct, just follow the note: specify a logbook via the -l parameter.
So if you logbook is called "linux", you enter
elogd -a youtheman -l linux |
|
47
|
Tue Jul 2 09:41:57 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Options <attribute> = List???? | > Hello,
> Is it possible to have a drop down list with commas in the options.
> For instance, if you want to have a attribute "CityState" you would
> probably want a comma between the City and State name. Since the Options
> are separated by commas, it turns into two different options. I dont know
> if there is a way to do this or if this is a bug?
From the next version on *2.0.4), one can specify attributes in quotation
marks like
Options town = San Francisco, "Paris, Texas", "Paris, France"
which then can include commas. |
|
60
|
Tue Jul 9 09:18:05 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Where can I get more information on the config file | > Where can I get more information about the config and themes file. I
> downloaded the latest version (2.0.4) and the config file docs seem out of
> date. I would like to get the icons working as well as getting the email
to
> work. The demo page at the elog home site shows both but I cannot find ant
> references to the icons.
Oops, I forgot the "IOptions" statement to documentation. Please see the
updated version at
http://midas.psi.ch/elog/config.html
look for "IOptions". For the Email notification see the whole
section "Email
notification" near the bottom of the page. |
|
61
|
Tue Jul 9 09:25:41 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: problem saving elogd.cfg | > In version 2.0.4 of eLog I was having some problems with saving my
> configuration file once I edited it on the web using the config. command.
> I keep getting the message "Cannot open file %s: elogd.cfg". I made sure
> the file was in the right directory. I dont know if I am doing something
> wrong or if its a bug?
The error display is certainly wrong. I fixed that and you can download the
updated version at
http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
As for the error, you should check the file permissions. If you run the
daemon under a user which has no write access to the directory or file, you
would get the described error. |
|
69
|
Thu Jul 11 16:03:56 2002 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: entry number not updated properly after deleting | > Hello,
> If you delete a message from the middle of a logbook that contains a
> bunch of messages, the message numbers do not get updated properly. For
> instance, if you have 20 messages in the logbook, and delete number 15,
> entry numbers 16 through 20 all do not get subtracted by one; their numbers
> stay the same with #15 just missing in the middle.
>
> Mo
That's how it's supposed to be. Once a unique message ID is attached to a
message, it stays there forever. Think of links to message like
http://midas.psi.ch/elogdemo/Forum/68
If you have such a link in a message or as a bookmark in your browser, and
the ID gets changed from 68 to 67, then your link would be off. |
|