| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1269
|
Thu Jul 14 17:34:12 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | | Re: short/long_name should point the same user |
| Emiliano Gabrielli wrote: | In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
 |
Well, that teaches you not to do this error again  |
|
1270
|
Thu Jul 14 19:11:54 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: short/long_name should point the same user |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
|
Well, that teaches you not to do this error again |
uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works ..  |
|
1272
|
Thu Jul 14 20:24:07 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | | Re: short/long_name should point the same user |
| Emiliano Gabrielli wrote: | uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. |
The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist |
|
1273
|
Fri Jul 15 15:03:01 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: short/long_name should point the same user |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. |
The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist |
uhmm .. what I am talking about is something simpler ... It seems to me that elog does not use always the "login name" but somethins refers to the "gecos" ... What I'm askinf for is to separe the login name (to which elog has to refer for everything internally) and the long/short_name mechanism that should be a mere display issue ...
May be that it is the same to ask for the introdution of a "user_id" or to treat the login name as the uid, .. the "Author" field should be filled both with the long and the short name (and it is so now!) but, when checking the original author on a Edit action, aelog as to check always the actual logged *short* name against the original Author *short* name .. becoise is only the short name that should have a sense for messages .. the long one is only a nice reminder
Hope my english makes me to be understod now |
|
68817
|
Wed Jun 6 02:41:32 2018 |
| Xuan Wu | wux@ihep.ac.cn | Question | Linux | 3.1.2 | Re: shiftcheck restrict edit |
Is there a way to restrict other author to edit the custom input form submitted?
| Xuan Wu wrote: |
|
Hi all,
There are options "Restrict edit" and "Restrict edit time" for general logbooks, but it seems not work for shiftcheck logbook. I think the function only author can change their own entry is necessary for shiftcheck too. Any suggestion would be hightly appreciated.
Cheers,
Xuan
|
|
|
1180
|
Mon Jun 6 12:43:48 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | 2.6.0-beta | Re: shell exec not working |
| Emiliano Gabrielli wrote: | It seems that, since Fri 2005-06-03, 12:50 almost, the shell exec feature is not invoked anymore.
the -x flag is present in the command line and the elog.cfg Parameters are present both for edit and for insert..
I'm not disabling shell exec by the checkbox
the dummy-level log in syslog does not show *anything* about shell exec. |
oh my @#[#@ .. sorry stefan, my bad ... for some reason the make_thumbs script was not +x ..
Is it possible to check the executability of the script in elog and eventually tell about this in syslog ?  |
|
1612
|
Thu Jan 19 17:05:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.x | Re: settings for "show only new entries" |
| Ulrich Trüssel wrote: | how ca i set the date for the "show only new entries" button? maybe i missed somethin on the elog.cfg description?
thank's for hint! |
That button works as follows: When you are active browsing entries, your activity is recorded (only the time) in the password file. Now when you are inactive for more than one hour, you are considered "logged out", and your last activity is taken as a filter for new entries. That means you see new entries since your last activity in the logbook. If you want to see the last day/week/month etc. you can define a quick filter on the date instead. |
|
99
|
Sat Aug 10 13:00:26 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: self-registration |
> i seem to be unable to find a clear explanation of how to enable self-
registration in the docs.
>
> just to be sure i grepped the doc directory, but the two references to it
were in the changelog and the faq.
>
> it could be just me but i'm not reading between the lines or connecting the
various places in the docs to get it going :/
Sorry, I haven't fully documented it yet, will do on Monday next week. For
now, see the configuration file for this forum which is attached. |