ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 59 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6444 Entries

Goto page Previous 1, 2, 3 ... 58, 59, 60 ... 804, 805, 806 Next

Thu Feb 28 19:07:19 2008

#include statements and attachment visibility

Hi!

First of all, thank you again for the great software and all the support.

Recently, one collaborator here noted that it would be helpful if the preview of attached files could be disabled on a file-by-file basis (via a checkbutton next to the "Upload" button maybe?). This applies e.g. to cases where someone performs a measurement outside of routine operations and attaches the ASCII data file (preview not wanted, in particular if it contains many lines) and the graph representing the evaluation (preview wanted). The disabling should apply to both single-entry view and list view with "Show attachments" option.

Another "fancy" idea of ours would be to allow #include-like statements in the ELOG config file. E.g. if the number of logbooks gets large, people might choose to put old logbooks to an archive disk which is then stored on some shelf. If a user then wants to access these, the disk could be mounted again (say, under /elog-archive). But since we don't know which archive disk has been mounted, and in order to keep the main config file small, the best would be to have the configurations for the logbooks of each disk on the disk itself (say, in a file called additional.config). We could then have a line like

#include /elog-archive/additional.config

in the main config file. When the elogd is (re)started, it would try to include that file. If it finds none (because no archive disk is mounted) it would silently ignore this. But if it finds such a file, it would include the logbook definitions found therein.

Do you think it is possible (and preferable) to implement this?

Cheers

Y

65771

Thu Mar 6 18:19:48 2008

Re: #include statements and attachment visibility

Thanks you! I just installed the new revision, and it works.

However, it does not seem to work in list mode (with attach=1 option): elog still shows all the lines of attached text files there.

I also noticed that the images referenced inline are also shown in the attachment list in list mode, although this post gave me the impression that in list mode, too, inline images should only be displayed inside the elog entry and not in addition as attachment.

Might this be a bug, or is there a particular reason why it is like that?

65773

Fri Mar 7 13:07:34 2008

Re: #include statements and attachment visibility

Thank you, works perfectly!

65817

Wed Apr 9 14:41:12 2008

Problems with elog client

Hi!

Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.

Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.

Any ideas?

Yoshio

65822

Thu Apr 10 14:21:13 2008

Re: Problems with elog client

I have tried the new revision, recompiling both client and server.
Unfortunately, the overall situation has not changed. We can still create new entries using the elog client, but editing an existing entry still does not work. However, thanks to your patch, the -v option now works again for the client side:

> elog -s -h <elog server> -p 443 -l current -u <user> <password> -a <Attributes> "TEST ENTRY"
Message successfully transmitted, ID=1

> elog -s -h <elog server> -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host <elog server>, port 443
Request sent to host:
GET /current/1?cmd=download HTTP/1.0
User-Agent: ELOG
Cookie: unm=<user>;upwd=<password>;


Response received:
ET
Error transmitting message

Again, there is no output on the server side even when running with -v in console mode. There is the expected output when an entry is successfully created using the elog client. One aspect about this output is strange, though: the "Return" statement

==== Return ================================
HTTP/1.1 302 Found

contains the wrong "Location" header. It is not

Location: https://elog-server.domainname/logbook/ID

but rather

Location: https://client-host.domainname/logbook/ID

where "client-host" is the hostname of the computer where the elog client was called. But, since the logbook entry is correctly created, this is perhaps not a problem at all.

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?

Cheers

Yoshio

65824

Thu Apr 10 15:56:12 2008

Re: 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

65834

Thu Apr 17 19:11:36 2008

Re: 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

65842

Fri Apr 18 14:17:52 2008

Re: Problems with elog client

Stefan Ritt wrote:

I fixed that in SVN revision 2103, please download and test it.

I just downloaded and tested it. It works!!

Thank you for all the work.

Yoshio

Goto page Previous 1, 2, 3 ... 58, 59, 60 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6