Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 659 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  65823   Thu Apr 10 15:39:26 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2099Re: Problems with elog client

Yoshio Imai wrote:
> elog -s -h elog -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host elog, port 443


As I wrote in my previous message, the "SSL part has not been tested" (=means: does not work). I just fixed this today, so try revision 2100.
  65824   Thu Apr 10 15:56:12 2008 Agree Yoshio ImaiBug reportLinux2.7.3-2100Re: Problems with elog client

Stefan Ritt wrote:
As I wrote in my previous message, the "SSL part has not been tested" (=means: does not work).


Sorry for the misunderstanding. I was probably confused because the creation of new entries already worked, even with SSL.
Now, the editing also works.

Thank you very much!

Yoshio
  65831   Tue Apr 15 20:34:49 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2099Re: Problems with elog client

Yoshio Imai wrote:
Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare the conditions once, e.g.
Options Category = .... , Shift {1} , ....
{1} Options Subject = Shift start {a}, Shift end {b}, ....

but the preset text declarations
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt
have to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?


I cannot reproduce your problem. I just tried following file:
[global]
port = 8000
password file = passwd
Options Category = Other , Shift {1} , Routine
Attributes = Author, Category, Subject
{1} Options Subject = Shift start {a}, Shift end {b}
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt

[demo1]
Comment = General linux tips & tricks

[demo2]
Comment = General linux tips & tricks

and it worked as expected. Can you try it? If it works for you as well, then try to morph this file towards your config file, and figure out when the unexpected behavior starts.
  65834   Thu Apr 17 19:11:36 2008 Reply Yoshio ImaiBug reportLinux2.7.3-2099Re: Problems with elog client
I have tried your sample config file, and this one also works for me.
The problem arises when using top groups. I have produced a minimal config file including a top group, of the form
[global]
logbook tabs = 1
SSL = 1
Theme = default

Top group testgroup = demo1, demo2
Show top groups = 1


[global testgroup]
Attributes      = Author, Subject, Type
Options Subject = ThisOne{1}, Shift info {2}, ThatOne{3}

{1} Options Type = OneType1, OneType2, OneType3
{2} Options Type = Shift start {a}, Shift end {b}, Info
{3} Options Type = TwoType1, TwoType2, TwoType3

Required Attributes = Author, Subject, Type

{2&a} Preset Text = shift_checklist.txt
{2&b} Preset Text = shift_summary.txt


[demo1]
Comment = DemoLog 1

[demo2]
Comment = DemoLog 2

Although the conditional attributes work for the logbooks demo1 and demo2, the preset text does not work. It works when the Preset Text= statement is (also) places in the individual logbook sections. Can you check if it behaves the same on your side?

Yoshio
  65837   Thu Apr 17 21:23:06 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2099Re: Problems with elog client

Yoshio Imai wrote:
The problem arises when using top groups.


Uff, that was a tough one. Thanks to your detailed analysis I could reproduce the problem. It indeed only happens with conditional 'preset text' under a top group (which is so exotic I have never tried it before). I fixed that in SVN revision 2103, please download and test it.
  65838   Thu Apr 17 22:17:05 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.3-2058Re: conditional options are not working in find

Arno Teunisse wrote:

Would be nice if the user can search with the same items he used entering the data into the form.

I finally found some time to implement conditional attributes in the find form. This new feature is contained in SVN revision 2104 and in the Windows version 2.7.3-3.

  65839   Thu Apr 17 22:40:12 2008 Reply Arno TeunisseA.teeling3@chello.nlBug reportWindows2.7.3-2058Re: conditional options are not working in find

Stefan Ritt wrote:

Arno Teunisse wrote:

Would be nice if the user can search with the same items he used entering the data into the form.

I finally found some time to implement conditional attributes in the find form. This new feature is contained in SVN revision 2104 and in the Windows version 2.7.3-3.

Hello Stefan

Just downloaded the windows version. It is working great !! Thanks, for this quick solution.. and you're time..

Just like elog more and more...

 

 

  65840   Thu Apr 17 23:20:50 2008 Reply Arno TeunisseA.teeling3@chello.nlBug reportWindows2.7.3-2058Re: conditional options are not working in find

Arno Teunisse wrote:

Stefan Ritt wrote:

Arno Teunisse wrote:

Would be nice if the user can search with the same items he used entering the data into the form.

I finally found some time to implement conditional attributes in the find form. This new feature is contained in SVN revision 2104 and in the Windows version 2.7.3-3.

Hello Stefan

Just downloaded the windows version. It is working great !! Thanks, for this quick solution.. and you're time..

Just like elog more and more...

 

 

Just noticed that in IExplorer and Firefox when creating a new entrie i got a popup with the following text in it : Unknown toolbar item "ShowBlocks"

When clicking OK : everything is working. Think it has to do with FCKedit, but I'm not shure.

 

ELOG V3.1.5-3fb85fa6