ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 176 of 238

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

1898 Entries

Goto page Previous 1, 2, 3 ... 175, 176, 177 ... 236, 237, 238 Next

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 Frown

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:

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 ...

TIMEZONE modifier?, posted by Steve Jones on Mon Apr 10 05:34:40 2006

We host eLog for a number of global sites. Our logbooks use datetime attributes but the timezones are wrong attributes that are either preset (like when a logentry is created) or if we fill in an attribute from an action (like when a logentry is closed). Any possibility of adding a timezone designator to FORMAT or does one already exist?

Thanks!

elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Tue Mar 14 17:51:52 2006

Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment.

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Stefan Ritt on Wed Mar 15 09:28:42 2006

Steve Jones wrote:

Steve,

again I could not reproduce your problem. See the attached screenshots. It just works fine with me (of course I miss the HTML files for the header and footer). I use however the most recent version of elog (Revision 1675). I also have a different password file. So try the following:

- look into your password file (it's a simple XML text file), it should contain something like

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

- make sure that you have the most recent version of elogd. Try at least elog261-3.exe under Windows.

- are you sure you need top groups? Top groups are ment for groups of logbooks which are completele unrelated, like from different departments, with different admins etc. Historically top groups were implemented because some elog installations had several elogd servers running in parallel for different departments. In you case, I suspect that "normal" groups might be enough, like:

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Wed Mar 15 21:42:25 2006

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

Aacck! I thought sure that this would do it for you. Ok, to answer your last question first:
1> I am reasonably sure that I need top groups. The logbooks with the -CL extension have a common attribute structure. The logbooks with the -IL extension have a common attribute structure. Neither group is the same. Prior to using Top Group I was using a global config for the -CL's but manually maintaining consistent -IL configs was horrible. Top Group solved my problem: maintaining only two config "areas" as opposed to many is very efficient. Do you have another way of doing this other than running two instances of eLog?

2> My password file on Windows is

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

3> I see your screen shots. Try going in and creating a new logbook and tell me if it dies. In the meantime is the latest version available in compiled form for Windows? If so, I'll install it and try again. At this point I am looking at starting a new config file from scratch but unless you can suggest another way I think Top Group is my only option.

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Wed Mar 15 23:46:54 2006

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

Ok, I completed stripped any attributes and only defined top groups. eLog no longer crashes but returns a completely invalid page with invalid links when I attempt to create a new logbook - see screenshot below. This is good as it means something in the config was causing things to blowup. I have also attached my stripped out config.

Incidently, I added another screenshot - an invalid link when I *delete* a logbook gets returned "http://localhost:8080/Test4-CL/Engineering%20Compute%20Change%20Logs/". Definitely not a correct URL.

Quote:

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Tue Mar 21 00:05:43 2006

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Wed Mar 15 09:22:02 2006 -->
<list>
  <user>
    <name>stefan</name>
    <password>zFDkjoZsg==</password>
    <full_name>Stefan Ritt</full_name>
    <email>stefan.ritt@psi.ch</email>
    <last_logout>Thu Feb 23 15:35:19 2006</last_logout>
    <last_activity>Wed Mar 15 09:22:02 2006</last_activity>
    <email_notify>
      <logbook>demo</logbook>
    </email_notify>
  </user>
</list>

Group Engineering Compute Change Logs = TX11-CL, TX30-CL, TX32-CL, AZ34-CL, AZ50-CL, FL29-CL, IL108-CL, IL05-CL, Approvals-CL, Template-CL
Group Engineering Compute Incident Logs =  TX11-IL, TX30-IL, TX32-IL, AZ34-IL, AZ50-IL, FL29-IL, IL108-IL, IL05-IL, Template-IL

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Mar 14 10:35:04 2006 -->
<list>
  <user>
    <name>r4aajl</name>
    <password>TDIwYXVyZW4=</password>
    <full_name>Steve Jones</full_name>
    <last_logout>0</last_logout>
    <last_activity>Tue Mar 14 10:35:04 2006</last_activity>
    <email>steve.jones@freescale.com</email>
    <email_notify>
      <logbook>TX30-CL</logbook>
      <logbook>TX11-CL</logbook>
      <logbook>TX32-CL</logbook>
      <logbook>AZ34-CL</logbook>
      <logbook>AZ50-CL</logbook>
      <logbook>Approvals-CL</logbook>
      <logbook>FL29-CL</logbook>
      <logbook>IL108-CL</logbook>
      <logbook>ZIL05-CL</logbook>
      <logbook>Template-CL</logbook>
    </email_notify>
  </user>
</list>

Steve Jones wrote:

BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Stefan Ritt on Mon Apr 3 17:09:19 2006

Steve Jones wrote:

There is a 2.6.1-4 version for Windows for download, which contains the most recent code.

Re: elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Fri Apr 7 05:07:20 2006

Stefan Ritt wrote:

Steve Jones wrote:

There is a 2.6.1-4 version for Windows for download, which contains the most recent code.

Quote:

Ok, I loaded the new Windows version ELOG V2.6.1-1681. The new version has the same behavior and it is entirely related to Top Group. With a simple Top Group setup things appear to work fine until one attempts to either create or delete a new logbook. There are other quirky things - I don't think Top Group is ready for really complex setups. In fact, this URL that is constructed by elog (http://localhost:8080/Engineering%20Compute%20Change%20Logs/Test/?cmd=Config) will cause elog to coredump but only with a very complex configfile. If I simply remove the "Top" from the "Group" directive I get the expected message "Error: logbook "Engineering Compute Change Logs" not defined in elogd.cfg
Please use your browser's back button to go back".

Another interesting point of reference - I went back to 2.5.9-4 (windows) and get the same behavior.

Now, making things really simple I added Top Group support to the demo that comes with the Windows install. This configfile:

[global]
port = 8080

Show top groups = 1
Top Group Demo Groups = demo, test7

[global Demo Groups]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[demo]

results in this redisplay after a new logbook create I have included in an attached screenshot. Please note that everything is generally not correct. So, even though eLog does not crash with this simple config it does support my observation that as I render the congfile more complex I corrupt eLog more until it finally crashes. Stefan, I would be interested in seeing how the above config runs on one of your windows systems.

Triggering $shell question, posted by Steve Jones on Wed Apr 5 20:25:42 2006

Should this work? rev1684 now allows $shell to pass attribute contents to the shell command and whenever a new entry is submitted or when one Edits/Replys the Subst is triggered, but I would like to be able to trigger this whenever a new value in the options pulldown is selected (assume Risk2 and Risk3 are identical to Risk1). Being able to trigger a regular Preset works fine (like {1} preset Date = $date ) but I would like to trigger the Subst. Maybe a better question, what actions (Subst, Preset, Change, Execute, etc.) I've tried Subst and Preset but not much luck.


##################################################
# Define Risk1
#
Options Risk1 = 10{30}, 20{31}, 30{32}, 40{33}, 50{34}, 60{35}, 70{36}, 80{37}, 90{38}, 100{39} 
{30,31,32,33,34,35,36,37,38,39} Subst TotalRisk = $shell(gawk 'BEGIN{ print $Risk1 + $Risk2 + $Risk3 }' )

Re: Triggering Re: Triggering $shell question, posted by Steve Jones on Wed Apr 5 22:48:49 2006

Steve Jones wrote:


##################################################
# Define Risk1
#
Options Risk1 = 10{30}, 20{31}, 30{32}, 40{33}, 50{34}, 60{35}, 70{36}, 80{37}, 90{38}, 100{39} 
{30,31,32,33,34,35,36,37,38,39} Subst TotalRisk = $shell(gawk 'BEGIN{ print $Risk1 + $Risk2 + $Risk3 }' )

Hmm, maybe I can answer my own question - until the form is saved with the new value selected the old values still exist. I guess what I really need is to trigger the $shell anytime a save happens or logentry is pulled in for edit. I think I do the latter with Subst on edit/Subst on Reply, but how on any save?

. . . Except that when I change an options field that has a dependencies, doesn't the javascript force a server-side revalidation?

Goto page Previous 1, 2, 3 ... 175, 176, 177 ... 236, 237, 238 Next

ELOG V3.1.5-3fb85fa6