Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 309 of 806  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  67328   Thu Aug 30 09:13:57 2012 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2473Re: Difference between time and date formats
OK, I see that $date can work in a different way; if the Thread display uses $date,
then the present timestamp is substituted into the thread display line, rather than the 
date that the entry is entered.  So, for example, in a whole list of entry and replies, the present
date shows on each entry of the thread.  However, the format is still that as defined by
'Time format' rather than 'Date format'.

If nothing else, I cannot really see the point of the 'Date format =' in the way that this all works.

> Hi,
> 
> I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats
> 
> Extract from my elog.cfg file:
> 
> 
> Time format = %a %d %b %y
> Date format = %d %b
> Thread display = $Ticket: $System, $entry time. ($message id). $status
> Preset text = [$date]
> Prepend on reply = [$date] \n
> 
> I can point to places in the syntax doc where each of these lines are given.
> 
> As for the results, the thread display is (for example):
> 
> T00001: Computer, Wed 29 Aug 12. (1). Problem
> 
> However, what I get at the top of the text box in starting a new entry or replying to a previous one is
> 
> [Wed 29 Aug 12]
> 
> whereas I expected to get
> 
> [29 Aug]
> 
> Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference
> 
> I cannot see where I'm going wrong.  
> 
> TIA 
> 
> David.
  67327   Wed Aug 29 22:44:39 2012 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2473Difference between time and date formats
Hi,

I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats

Extract from my elog.cfg file:


Time format = %a %d %b %y
Date format = %d %b
Thread display = $Ticket: $System, $entry time. ($message id). $status
Preset text = [$date]
Prepend on reply = [$date] \n

I can point to places in the syntax doc where each of these lines are given.

As for the results, the thread display is (for example):

T00001: Computer, Wed 29 Aug 12. (1). Problem

However, what I get at the top of the text box in starting a new entry or replying to a previous one is

[Wed 29 Aug 12]

whereas I expected to get

[29 Aug]

Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference

I cannot see where I'm going wrong.  

TIA 

David.
  67326   Wed Aug 29 18:16:37 2012 Reply Szu-Ching Pecknerspeckner@nd.eduQuestionLinuxlatestRe: secure way to allow users create logbook

Stefan Ritt wrote:

Szu-Ching Peckner wrote:

I don't think there is a good secure way so far, but would like to have your opinion. 

If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

 Is there a way to set user permission based on certain attribute? can Allow command = <user list> based on attribute?
for example, say type home, user1 can read, user2 can write, user3 can not access type home, but can access type work. 

In short, is access control available when I use type to get functionality of separate logbooks? If so, how is this access control done? 

 

 

  67325   Wed Aug 29 17:55:37 2012 Agree Zbigniew Reszelareszelaz@gmail.comQuestionLinuxV2.8.1-235Re: dynamic preset text

Stefan Ritt wrote:

Zbigniew Reszela wrote:

Dear all,

Is it possible to have a dynamic "preset text" option?

I would like to switch the template file depending on the attribute value. (Of course this attribute values will be a fixed list of options, not extandable). 

I see there one difficulty, that: if user already started editing the text body, he could lose this data. But I think that this could be left on user responsibility to take care about it.

Another option could be to always insert the template text on the very beginning of the text body.

Is this feature implemented, or maybe someone have done it by changing the server code?

Cheers

This is possible with conditional attributes. An additional trick would be to not show the text body of an attribute is not selected. This way the user first has to select the attribute, then the text field with the specific preset will show up. The configuration would be something along these lines:

 

Attributes = Type, Subject
Options Type = One{1}, Two{2}, Three{3}
Show text = 0

{1} Preset text = text1
{2} Preset text = text2
{3} Preset text = text3
{1,2,3} Show text = 1

 

Of course you have to supply proper text files text1, text2, text3.

- Stefan

 

 Thanks, it works perfectly!

  67324   Wed Aug 29 14:35:45 2012 Agree Szu-Ching Pecknerspeckner@nd.eduQuestionLinuxlatestRe: secure way to allow users create logbook

Stefan Ritt wrote:

Szu-Ching Peckner wrote:

I don't think there is a good secure way so far, but would like to have your opinion. 

If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

 Thanks, that is good option. 

  67323   Wed Aug 29 10:46:49 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxlatestRe: secure way to allow users create logbook

Szu-Ching Peckner wrote:

I don't think there is a good secure way so far, but would like to have your opinion. 

If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

  67322   Wed Aug 29 10:37:44 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV2.8.1-235Re: dynamic preset text

Zbigniew Reszela wrote:

Dear all,

Is it possible to have a dynamic "preset text" option?

I would like to switch the template file depending on the attribute value. (Of course this attribute values will be a fixed list of options, not extandable). 

I see there one difficulty, that: if user already started editing the text body, he could lose this data. But I think that this could be left on user responsibility to take care about it.

Another option could be to always insert the template text on the very beginning of the text body.

Is this feature implemented, or maybe someone have done it by changing the server code?

Cheers

This is possible with conditional attributes. An additional trick would be to not show the text body of an attribute is not selected. This way the user first has to select the attribute, then the text field with the specific preset will show up. The configuration would be something along these lines:

Attributes = Type, Subject
Options Type = One{1}, Two{2}, Three{3}
Show text = 0

{1} Preset text = text1
{2} Preset text = text2
{3} Preset text = text3
{1,2,3} Show text = 1

 

Of course you have to supply proper text files text1, text2, text3.

- Stefan

  67321   Wed Aug 29 10:26:31 2012 Question Zbigniew Reszelareszelaz@gmail.comQuestionLinuxV2.8.1-235dynamic preset text

Dear all,

Is it possible to have a dynamic "preset text" option?

I would like to switch the template file depending on the attribute value. (Of course this attribute values will be a fixed list of options, not extandable). 

I see there one difficulty, that: if user already started editing the text body, he could lose this data. But I think that this could be left on user responsibility to take care about it.

Another option could be to always insert the template text on the very beginning of the text body.

Is this feature implemented, or maybe someone have done it by changing the server code?

Cheers

ELOG V3.1.5-3fb85fa6