ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66418
|
Thu Jun 25 12:30:17 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.6 | Re: Denial of access after failed import using invalid attributes |
soren poulsen wrote: |
Hi,
A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload.
1. suggestion : E-log should not crash in this case
2. suggestion: E-log should not allow invalid attributes to be added via CSV Import, which causes the log-book to be blocked.
For the time being, I will just "Deny import" (by the way, the doc says it is "Deny CSV import", but I think the syntax is "Deny import". Not really important.
I think this should be quite easy to reproduce.
Thanks a lot
Soren
|
If the CSV file contains a "date" column, elogd tries to interprete the date to the internal format. Now a date can be written in a huge number of variations, and I'm sure I did not cover all. So please send me your CSV file and I will fix the crash. |
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. |
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? |
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. |
67328
|
Thu Aug 30 09:13:57 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2473 | Re: 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. |
69296
|
Tue Feb 2 07:43:49 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | Unfortunately you have to name these top groups differently, because they are internally used for the database name.
MATT TERRON wrote: |
I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?
|
|
69297
|
Tue Feb 2 08:17:15 2021 |
| MATT TERRON | matao11235@gmail.com | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | So both Top Group names and Logbook names should be unique inside one .cfg file, is that correct?
Stefan Ritt wrote: |
Unfortunately you have to name these top groups differently, because they are internally used for the database name.
MATT TERRON wrote: |
I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?
|
|
|
69298
|
Tue Feb 2 08:25:46 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | That's correct.
Stefan Ritt wrote: |
Unfortunately you have to name these top groups differently, because they are internally used for the database name.
MATT TERRON wrote: |
I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?
|
|
|
|