Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 384 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 383, 384, 385 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66195   Fri Feb 6 11:46:18 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5Re: Options Category : User\Admin
Kim Rosmo wrote:

Thanks for a fast reply :)

Its a lot of html tutorials on the net, so i think i will make it with the tables ^^

Regarding the 'Options Category' I can live with it... I have removed edit mode in User, so only Admin can delete or edit.

One last question.. Background color possible?  (Not Style)

Only through style (that's what style is for, anyhow). 

  47   Tue Jul 2 09:41:57 2002 Reply Stefan Rittstefan.ritt@psi.chInfo  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.
  69273   Thu Dec 3 01:51:49 2020 Reply Harry Martinharrymartin772@gmail.comQuestionLinux | Windows3.1.3Re: Options <...> vs ROptions <...>

Same problem here, in version 3.1.3.   It would be very nice if this worked.

Wolfgang Bayer wrote:

According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

 

  69276   Thu Dec 3 09:58:44 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.3Re: Options <...> vs ROptions <...>

For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...

Harry Martin wrote:

Same problem here, in version 3.1.3.   It would be very nice if this worked.

Wolfgang Bayer wrote:

According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

 

 

  2062   Thu Nov 9 22:57:38 2006 Reply Stefan Rittstefan.ritt@psi.chRequestOther2.6.2-1739Re: Option to require new user registration to subscribe to ALL logbooks

Steve Jones wrote:
Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual.


The logbook list new users can register with is exactly the list the users have access to. So if you omit a logbook there, they can later just go to that logbook, hit config, and add themselves. If you want to prevent a user from getting notifications from a logbook, prevent user access to that logbook, like a new top group.


Steve Jones wrote:
Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application.


Not at the moment. It would take days of work which I don't have right now. Much more than what it takes you editing the password file in an editor Wink
  2066   Thu Nov 9 23:37:37 2006 Reply Steve Jonessteve.jones@freescale.comRequestOther2.6.2-1739Re: Option to require new user registration to subscribe to ALL logbooks

Stefan Ritt wrote:

Steve Jones wrote:
Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this to the "admin" user to pick per individual.


The logbook list new users can register with is exactly the list the users have access to. So if you omit a logbook there, they can later just go to that logbook, hit config, and add themselves. If you want to prevent a user from getting notifications from a logbook, prevent user access to that logbook, like a new top group.


Steve Jones wrote:
Also, any thoughts to adding a management panel that will the admin user to make global changes to the password file? I do this by bringing it into a text editor and making changes, but it would be nice to do it from the application.


Not at the moment. It would take days of work which I don't have right now. Much more than what it takes you editing the password file in an editor Wink



Quote:

Hmm, by default all users have access to all logs. What I have setup is an announcement logbook and I would simply like to send to all registered users the email when announcements happen. My thought was to simply not allow people to pick which logbooks to "register" with and default to the Announcements logbook. I went ahead and hacked the password file and simply set all accounts to subscribe to all logbooks Big grin
  66561   Fri Oct 16 12:21:45 2009 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.7.7Re: Option list length

soren poulsen wrote:

Hi,

I use the following attribute definition:

Options <attribute> = <list> 

However, I am being limited by the list length limit of 100. I have 103 items, but I only see 100.

Could the limit be extended (to 200 for instance) ?

Thanks a lot for your help

Soren

You can change that yourself. Just find following line in elogd.c:

 

#define MAX_N_LIST      100

and change it to 200, then recompile. But you are there on your own, at some point you will get a stack overflow and elogd will crash, but I don't know exactly where this limit is.
 
Anyhow I would propose that if you have so many options in an attribute, that you better go and group these options somehow. Like using two attributes, where the first defines the group, and the second gets different list for each option of the first attribute using conditional attributes. Have a look here.

 

 

  66564   Mon Oct 26 10:13:54 2009 Reply soren poulsensoren.poulsen@cern.chRequestLinux2.7.7Re: Option list length

Stefan Ritt wrote:

soren poulsen wrote:

Hi,

I use the following attribute definition:

Options <attribute> = <list> 

However, I am being limited by the list length limit of 100. I have 103 items, but I only see 100.

Could the limit be extended (to 200 for instance) ?

Thanks a lot for your help

Soren

You can change that yourself. Just find following line in elogd.c:

 

#define MAX_N_LIST      100

and change it to 200, then recompile. But you are there on your own, at some point you will get a stack overflow and elogd will crash, but I don't know exactly where this limit is.
 
Anyhow I would propose that if you have so many options in an attribute, that you better go and group these options somehow. Like using two attributes, where the first defines the group, and the second gets different list for each option of the first attribute using conditional attributes. Have a look here.

 

 

Thanks. This is a good explanation. It might indeed be better to re-group the options to have a shorter list.

Soren

Goto page Previous  1, 2, 3 ... 383, 384, 385 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6