ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65995
|
Mon Oct 13 10:37:27 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5-2130 | Re: Author field read only in new posts |
Brassmann wrote: |
Hi,
how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.
This is a part of my elogd.cfg
[global]
.......
Logfile = elogd.log Logging level = 3 Login expiration = 24 Password file = ./passwd
.......
[Informations]
.......
Logout to main = 1 Logbook tabs = 1 Guest menu commands = Back, Find, Login, Help Guest find menu commands = Find, Select, Login, Help
Preset Author = $long_name Attributes = Author, Subject Required Attributes = Author, Subject
........
Thanks Brassmann
|
All you need is an addition
Locked Attributes = Author
|
65994
|
Mon Oct 13 00:08:03 2008 |
| Brassmann | info@flash-networx.de | Question | Linux | 2.7.5-2130 | Author field read only in new posts | Hi,
how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.
This is a part of my elogd.cfg
[global]
.......
Logfile = elogd.log Logging level = 3 Login expiration = 24 Password file = ./passwd
.......
[Informations]
.......
Logout to main = 1 Logbook tabs = 1 Guest menu commands = Back, Find, Login, Help Guest find menu commands = Find, Select, Login, Help
Preset Author = $long_name Attributes = Author, Subject Required Attributes = Author, Subject
........
Thanks Brassmann |
65993
|
Sun Oct 12 20:40:32 2008 |
| Steve Nahn | nahn@mit.edu | Question | Linux | 2.7.4-2111 | Maximum number of mail recipients | Just wondering if there is still a maximum number of mail recipients? I saw a number of 112 floating around in old forum entries, and I need more, like currently 300. When I try it, the elogd hangs, not much output to speak of, but won't reply to Apache on its port. Any quick fix (like changing a def'd variable somewhere?) |
65992
|
Wed Oct 8 21:37:32 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: Deny Wildcards |
Neo wrote: |
I tried it in a global group configuration
[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1
But I as admin2 am still able to create new entries in the corresponding log books.
Is this configuration only for logbooks?
|
I just tried myself with following config:
[global]
port = 8080
password file = passwd
Allow New = joe
[demo1]
Theme = default
Attributes = Author, Subject
and it jus worked fine. When I'm not logged on as "joe", the "New" command even does not appear. If you would have supplied your correct ELOG version, I could have checked if you have an old version. In that case you could upgrade. |
65991
|
Wed Oct 8 15:31:49 2008 |
| Neo | Neo.X@web.de | Question | All | | Re: Deny Wildcards |
Stefan Ritt wrote: |
Neo wrote: |
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.
|
I tried it in a global group configuration
[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1
But I as admin2 am still able to create new entries in the corresponding log books.
Is this configuration only for logbooks? |
65990
|
Wed Oct 8 15:23:56 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: Deny Wildcards |
Neo wrote: |
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them. |
65989
|
Wed Oct 8 15:10:25 2008 |
| Neo | Neo.X@web.de | Question | All | | Deny Wildcards |
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ...
Allow New = admin1, admin2, admin3
Allow Edit = admin1, admin2, admin3
Deny New = *
Deny Edit = * |
65988
|
Mon Oct 6 08:41:58 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 2.7.2-2041 | Re: Summary lines spill over |
Ben Shepherd wrote: |
I've set up my ELOG configuration to display one summary line in the list view. However, a word from the next line creeps in from time to time. You can see this in my logbook - look at the 'Text' column for entries 805, 802 and 800 for instance. The word 'Shift' is from the second line of the entry, but it has been added to the summary text for some reason. Any ideas how I can fix this?
|
Your problem comes from the fact that you probably did not enter the HTML text body with the build-in editor, but copy-and-pasted it from somewhere else. ELOG determines the end of a line by looking at the line-feed character (\n), and your HTML text does sometimes not contain this character at the end, but only the HTML paragraph tag (</p>). I added some code in SVN revision 2131 to look also for the HTML tags properly, so if you upgrade to that version, it should be fine for you. |
|