ELOG Forum

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?

The problem had to do with the integration of native SSL into elog/elogd. I tried to fix it in revision 2099. Please give it a try. I have not tried yet the SSL mode, but I changed the -s for "subdir" to -d not to collide with SSL.

65820

Thu Apr 10 01:33:07 2008

Peter Freeman wrote:

Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.

Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.

Have looked arround here, but could not find anything in that direction.

Many thanks for any answer.

Peter

Nobody an idea if it is possible?

65821

Thu Apr 10 07:48:08 2008

Peter Freeman wrote:

Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.

Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.

Have looked arround here, but could not find anything in that direction.

Many thanks for any answer.

Peter

Nobody an idea if it is possible?

Sorry, I overlooked your first question.

Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:

- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"

- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.

- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background.

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

65823

Thu Apr 10 15:39:26 2008

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

65825

Fri Apr 11 00:15:42 2008

Stefan Ritt wrote:

Peter Freeman wrote:

Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.

Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.

Have looked arround here, but could not find anything in that direction.

Many thanks for any answer.

Peter

Nobody an idea if it is possible?

Sorry, I overlooked your first question.

Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:

- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"

- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.

- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background.

Danke Stefan, I check it out.

65826

Sat Apr 12 05:21:11 2008

Peter Freeman wrote:

Stefan Ritt wrote:

Peter Freeman wrote:

Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.

Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.

Have looked arround here, but could not find anything in that direction.

Many thanks for any answer.

Peter

Nobody an idea if it is possible?

Sorry, I overlooked your first question.

Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:

- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"

- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.

- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background.

Danke Stefan, I check it out.

Hmm, I'd like to use the style command, but it has no effect if I put it into the config. If I understood it right, it should be done this way:

Options Status = Open, Info, Resolved, Suspended, Waiting, Important
Style Status Important = background-color:red
Style Status Resolved = background-color:green

They are just showing up with the default style. Am I doing something wrong?

EDIT: Just downloaded the latest version and now it works. My old one was 2058, BUT, how can I change multiple styles, e.g. background and font color at the same time? Komma does not seem to work and two style lines also not.

Goto page Previous 1, 2, 3 ... 224, 225, 226 ... 799, 800, 801 Next

ELOG V3.1.5-3fb85fa6