Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 240 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66864   Wed Jul 28 17:01:06 2010 Reply Dennis Seitzdseitz@berkeley.eduRequestAll2.7.7Re: alphabetize Quick Filter items?

Stefan Ritt wrote:

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

 Hi Stefan,

I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.

We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.

I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?

Thanks again for a *very* useful logging system!

Dennis

The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items

Options Type = C, D, A, B

they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like

Options Type = A, B, C, D

I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.

- Stefan 

 Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!

 

Ok, I implemented

Sort attribute options = 1

in the current SVN revision. 

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?

You need revision 2252 or later. So you have to upgrade to 2.7.8. 

 We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?

  66866   Wed Jul 28 17:15:33 2010 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.7.7Re: alphabetize Quick Filter items?

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

 

Ok, I implemented

Sort attribute options = 1

in the current SVN revision. 

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?

You need revision 2252 or later. So you have to upgrade to 2.7.8. 

 We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?

Sorry, there was a typo, you need

Sort attribute options <attribute> = 1

where <attribute> is the name of the attribute to be sorted (in case you want some attributes sorted, but not all). 

  66870   Wed Jul 28 22:03:26 2010 Reply Dennis Seitzdseitz@berkeley.eduRequestAll2.7.7Re: alphabetize Quick Filter items?

Stefan Ritt wrote:

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

 

Ok, I implemented

Sort attribute options = 1

in the current SVN revision. 

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?

You need revision 2252 or later. So you have to upgrade to 2.7.8. 

 We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?

Sorry, there was a typo, you need

Sort attribute options <attribute> = 1

where <attribute> is the name of the attribute to be sorted (in case you want some attributes sorted, but not all). 

 That did the trick. That was a good idea, to give us the option of which attributes to sort, too. Thanks again for adding this feature!

  1815   Wed May 3 08:28:05 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: allow per-logfile attributes to be added/subtracted from the global settings

Mark Bergman wrote:
I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.


Sounds to me like a good idea. I will put it on the wishlist.
  67500   Fri May 10 17:37:24 2013 Reply Garret Delarondegarret.delaronde@gmail.comQuestionLinuxlatestRe: admin user access admin page, not config page

Szu-Ching Peckner wrote:

 We have multiple logbooks. Each user is admin user for his/her own logbook. 

I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user. 

[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config

user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them).  Is there a way after user1 click save, page doesn't go to that config page?

I could put 
Deny Change password =
Deny Remove user
Deny New user

so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page. 

 

 

 If they have admin rights, the add user button cannot be removed as far as I know.

But even if they can add a user, they only have ability to add a user to the single logbook they are an admin on so they wouldn't be able to add users to other peoples logbooks.

Not sure it helps but that's about all I can really speak to.

  859   Mon Dec 20 17:22:28 2004 Question Stefan Rittstefan.ritt@psi.chRequest  Re: admin menu
> Could you implemet and option 'admin menu' which gets displayed
> when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
> while the normal menu would not.

You can achieve the same via

Allow delete = <admin name>
  2059   Thu Nov 9 22:08:10 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: add field type to automatically email CC

Mark Bergman wrote:
I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.

I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.


For example (snippet of fictional elogd.cfg):

-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
-------------------------------


Just do the following:
Attributes = Author, Category, Notification list
Email all = $Notification list

Whenever you enter a new entry, you put a list of email addresses into the Notification list, which is then used for sending email addresses. This list also stays there in replies or edits.
  2078   Wed Nov 15 18:50:02 2006 Reply Arckonitcrashrunover@hotmail.comRequestLinux2.6.1Re: add field type to automatically email CC

Stefan Ritt wrote:

Mark Bergman wrote:
I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.

I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.


For example (snippet of fictional elogd.cfg):

-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
-------------------------------


Just do the following:
Attributes = Author, Category, Notification list
Email all = $Notification list

Whenever you enter a new entry, you put a list of email addresses into the Notification list, which is then used for sending email addresses. This list also stays there in replies or edits.



mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command

here is my config
Theme = default
Comment = Logs des modification de scripts des 3 domaines
Attributes = Acteur, Action, Type, Nom du Scripts, Language, Domaine, Categorie, Commentaires,Notification
Options Action = Ajout, Modification, Suppression, Réseau, Autre, Hotfix
Options Type = Ouverture de session,Autre, deploiement
Options Language = VBS, AU3, Kix, Batch, Ksh, Perl
Options Domaine = VaubanHumanis, Humanis, Vauban
Extendable Options = Catégorie, Type, Action
Required Attributes = Acteur, Type, Lieu
Page Title = Modification Scripts - $subject
Reverse sort = 1
Quick filter = Date, Type
Suppress Email to users = 1
# Email all = someadminsuser@maildomain.com
Email all = $Notification
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}

you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions
ELOG V3.1.5-3fb85fa6