Date automatically generated by another one, posted by Alex H on Thu May 4 17:26:41 2006
|
Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
Re: Date automatically generated by another one, posted by Stefan Ritt on Fri May 5 07:58:53 2006
|
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
|
Re: Date automatically generated by another one, posted by Alex H on Fri May 5 09:01:04 2006
|
| Stefan Ritt wrote: |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
OK! Thank for your response. |
allow per-logfile attributes to be added/subtracted from the global settings, posted by Mark Bergman on Wed May 3 00:16:42 2006
|
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.
For example, the [global] section of my elogd.cfg reads:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status
I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.
Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:
[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade
As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.
The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.
Thanks,
Mark |
|
Re: allow per-logfile attributes to be added/subtracted from the global settings, posted by Stefan Ritt on Wed May 3 08:28:05 2006
|
| 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. |
|
Any way to move Replies from one logentry to another?, posted by Steve Jones on Fri Apr 14 16:30:56 2006
|
| Is there anyway to reattach a reply within a logbook from one logentry to another? I guess it would be "re-associate"? |
|
Re: Any way to move Replies from one logentry to another?, posted by Stefan Ritt on Tue Apr 18 10:01:23 2006
|
| Steve Jones wrote: | | Is there anyway to reattach a reply within a logbook from one logentry to another? I guess it would be "re-associate"? |
No, this is not possible directly. You would have to make a new reply, and manually fill in the contents from the original reply. It is however possible by directly tampering the ELOG files, but that should be done only by experienced users. |
Re: Any way to move Replies from one logentry to another?, posted by Steve Jones on Wed Apr 19 04:48:43 2006
|
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Is there anyway to reattach a reply within a logbook from one logentry to another? I guess it would be "re-associate"? |
No, this is not possible directly. You would have to make a new reply, and manually fill in the contents from the original reply. It is however possible by directly tampering the ELOG files, but that should be done only by experienced users. |
Kind of what I thought but needed to ask. I think I'll leave things as they are. Thanks! |
|
User review..use case: implementing GTD, posted by Marco Calf on Sat Apr 15 00:37:48 2006
|
Playing with elog for a day made me very happy. I was looking for a webbased thingy to support list building for 'Getting Things Done' by David Allen ( David Allen's Getting Things Done ).
Elog is simple, intuitative and very powerfull!
Less informative is the fact that i found no bugs till now 
On usablitity..maybe some more control over the dialog..eg the 'in between' screens (eg after a move...the 'to which log i would like to resume' question)...or have an option to be in select mode by default.
Tnx |
|
Text Field color in Summary display, posted by Mike Jackson on Fri Apr 14 17:01:40 2006
|
| Is it possible to have the text field be the same color as the other attributes in the summary display? What I mean is how each line is a different color, but the text field is always white. I would like the text field to match the rest. I changed the .summary in the css file but it changes all the text fields, it doesn't allow them to alternate colors like the other fields on the summary display |
|
Can a field value be calculated during display?, posted by Sridhar Anandakrishnan on Wed Apr 12 19:22:34 2006
|
I have a logbook which is a Calendar/Appointment book with Attributes: "Appointment DateTime", Place, etc.
I would like another Attribute called "When" whose value is calculated from Today's Date - Appointment date (so for example I could display today's appointments in red...). This calculation has to take place each time the logbook is displayed...
Possible? Useful?
Thanks,
Sridhar. |
|
Re: Can a field value be calculated during display?, posted by Stefan Ritt on Thu Apr 13 09:07:24 2006
|
| Sridhar Anandakrishnan wrote: | I have a logbook which is a Calendar/Appointment book with Attributes: "Appointment DateTime", Place, etc.
I would like another Attribute called "When" whose value is calculated from Today's Date - Appointment date (so for example I could display today's appointments in red...). This calculation has to take place each time the logbook is displayed...
Possible? Useful? |
No.
ELOG is an electronic logbok and should not be used as a full calendar application. There are much better packages for that, like PHP groupware. Better use one of those packages. |
Problem with the "Forgot password?" option, posted by Hagelstein, Kay on Tue Apr 11 08:09:56 2006 
|
Hi,
I have a Problem with the "Forgot password?" option it doesn’t work with the “Top Group” option and the “Protect Selection page” option.
Is this a bug or a Problem in my Configuration?
The elog Version is V2.6.1-1681
Regards
Kay |
|
elog client authentication and attachment comment, posted by Yoshio Imai on Thu Apr 6 20:24:06 2006
|
Hi again!
I have two questions, one concerning authentication methods for the elog client. Until revision 1642, it was possible to submit entries to a password-protected logbook using the elog client without supplying authentication information. With revision 1671 this is no longer possible. In principle this is good. However, many of our run control programs use the elog client (via rsh to the elog server computer) to submit automatic entries, which fails now. In order for this mechanism to work again, we would have to change the command-line call in the sources, including now the password in clear text. Since this can be considered a security issue, we would like to avoid it if at all possible. I guess my request would go in the direction of PAM support, but would it be possible to revert to the old behaviour as an option? (If you tell me where in the code to look, we could probably also comment out the respective lines ourselves so that you don't have extra work...)
The second remark is about attachment comments. When editing a logbook entry, the attachment upload buttons appear again, but without the comment. Shouldn't it be there, too?
Thanks,
Yoshio |
|
Re: elog client authentication and attachment comment, posted by Stefan Ritt on Fri Apr 7 10:29:49 2006
|
| Yoshio Imai wrote: | | Until revision 1642, it was possible to submit entries to a password-protected logbook using the elog client without supplying authentication information. With revision 1671 this is no longer possible. In principle this is good. However, many of our run control programs use the elog client (via rsh to the elog server computer) to submit automatic entries, which fails now. In order for this mechanism to work again, we would have to change the command-line call in the sources, including now the password in clear text. Since this can be considered a security issue, we would like to avoid it if at all possible. I guess my request would go in the direction of PAM support, but would it be possible to revert to the old behaviour as an option? (If you tell me where in the code to look, we could probably also comment out the respective lines ourselves so that you don't have extra work...) |
There was a quite strong request to not allow unauthorized access via the elog utility. People were also able to submit entries with the "curl" program without supplying authorization. So I rather would not like to go back to the old version. But I would propose a different scheme: We could save the username/password in a file on the server, which is maybe readable only by the owner. Then one could call elog with
elog ... -u @filename
so that the user name and password gets retrieved from the file on the server. This way the password does not have to be passwd over the network. BTW, you also could use ssh instead of rsh to prevent password being sent over the network in plain text.
| Quote: |
The second remark is about attachment comments. When editing a logbook entry, the attachment upload buttons appear again, but without the comment. Shouldn't it be there, too? |
I'll have a look and fix it. |
|
Re: elog client authentication and attachment comment, posted by Yoshio Imai on Mon Apr 10 20:08:02 2006
|
| Stefan Ritt wrote: | | We could save the username/password in a file on the server, which is maybe readable only by the owner. |
I have discussed it with the others, and it sounds like a good idea. There is only the debate whether it should be readable by the owner or by the root user of the elog server. I can't tell at the moment which is more favourable ... |