Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 14:21:13 2008
|
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 notLocation: https://elog-server.domainname/logbook/ID but ratherLocation: 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.txthave to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?
Cheers
Yoshio |
|
Re: Problems with elog client, posted by Stefan Ritt on Thu Apr 10 15:39:26 2008
|
| 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. |
|
Re: Sticky entries?, posted by Peter Freeman on Fri Apr 11 00:15:42 2008
|
| Stefan Ritt wrote: |
|
| Peter Freeman 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. |
|
Re: Sticky entries?, posted by Peter Freeman on Sat Apr 12 05:21:11 2008
|
| Peter Freeman wrote: |
|
| Stefan Ritt wrote: |
|
| Peter Freeman 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. |
|
Re: attachment indicator in summary view, posted by Grant Jeffcote on Sat Apr 12 22:04:58 2008
|
Hi Stefan,
When using 2.7.3-2095 I can't seem to get the paperclip/s to show, just an additional field in the summary view (named Attachments) with the attachment file names below? Am I missing something?
Thanks
|
Dennis Seitz wrote
|
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.
|
Nice idea. I implemented that feature, as can be seen at the contributions logbook for example. It will be contained in the next release.
|
Thanks!
|
|
|
Re: attachment indicator in summary view, posted by Stefan Ritt on Sun Apr 13 16:04:09 2008
|
| Grant Jeffcote wrote: |
|
When using 2.7.3-2095 I can't seem to get the paperclip/s to show, just an additional field in the summary view (named Attachments) with the attachment file names below? Am I missing something?
|
Yes, you miss the paperlclip icon. Get it from here and copy it under elog/themes/default/attachment.png. |
|
Re: Sticky entries?, posted by Stefan Ritt on Mon Apr 14 08:46:41 2008
|
| Peter Freeman wrote: |
|
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.
|
You can separate them with a semicolon. Just like:
Style Category Info = background-color:lightblue;font-weight:bold
Note that you cannot change the font color, since it is a link, and that is defined in the default.css file under
/* standard link colors and decorations */
a:link { color:#0000FF; text-decoration:none }
a:visited { color:#800080; text-decoration:none }
a:hover { color:#0000FF; text-decoration:underline }
a:active { color:#0000FF; text-decoration:underline }
a:focus { color:#0000FF; text-decoration:underline }
|
|
Re: Problems with elog client, posted by Stefan Ritt on Tue Apr 15 20:34:49 2008
|
| 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.txthave 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. |
|