ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66821
|
Fri May 14 17:03:36 2010 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8-2294 | Re: Required Attributes |
| Eric Krise wrote: |
|
Is there a way to require a certain attribute on reply, but not on an original entry? In some cases info. for these fields only exists on reply.
|
No. There is only "Preset on reply ..." and "Remove on reply...". You could for example require that attribute, preset it for new entries with some dummy value, and remove that value with "Remove on reply...". Maybe that works. |
|
66820
|
Fri May 14 16:53:54 2010 |
 | Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Required Attributes |
Is there a way to require a certain attribute on reply, but not on an original entry? In some cases info. for these fields only exists on reply. |
|
66819
|
Fri May 14 16:50:53 2010 |
| Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Re: Entry merging |
| Stefan Ritt wrote: |
|
| Eric Krise wrote: |
|
Is there a way to merge existing entries from several logbooks into a single logbook?
|
Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook.
|
Got it! Thanks... |
|
66818
|
Fri May 14 08:57:07 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8-2294 | Re: Entry merging |
| Eric Krise wrote: |
|
Is there a way to merge existing entries from several logbooks into a single logbook?
|
Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook. |
|
66817
|
Thu May 13 13:31:53 2010 |
| Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Entry merging |
Is there a way to merge existing entries from several logbooks into a single logbook? |
|
66816
|
Wed May 12 16:30:45 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8-2293 | Re: HTML email format displays plain text if email client is offline |
| Jim Covert wrote: |
|
My elog server is hosted behind a firewall and I use a VPN client to connect to the network on which it is hosted. When I'm logged into the VPN emails from elog display fine, but when I'm not connected to the VPN emails display in plain text because the email client is unable to load "default.css" since it's behind a firewall.
Is there a way to include the style information in the HTML email rather than in a separate file that's hosted on the elog server?
|
That's a good idea. I will consider that for a future version. |
|
66815
|
Tue May 11 19:14:37 2010 |
| Jim Covert | jim.covert+elog@gmail.com | Question | Windows | 2.7.8-2293 | HTML email format displays plain text if email client is offline |
My elog server is hosted behind a firewall and I use a VPN client to connect to the network on which it is hosted. When I'm logged into the VPN emails from elog display fine, but when I'm not connected to the VPN emails display in plain text because the email client is unable to load "default.css" since it's behind a firewall.
Is there a way to include the style information in the HTML email rather than in a separate file that's hosted on the elog server? |
|
66814
|
Mon May 10 09:55:12 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Other | 2.7.8 | Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message |
Hi Rouilj,
re-posting your bug report doe not help. If I'm not replying immediately it means I'm pretty busy with other things, so just be patient.
Your problem is related to the reply from the server you posted. After you send
GET /Discussion/?cmd=GetPwdFile
you should get the login page, which starts with
HTTP/1.1 200 Document follows
....
<title>ELOG Login</title>
....
but you do get
HTTP/1.1 404 Not Found
....
The best thing to diagnose this problem is to run the server with the "-v" flag, so you don't have to run truss. Then compare the request sent by your cloning process (your GET /Discussion/?cmd=GetPwdFiel from above) and compare it if you send from your browser
http://host.example.org:8080/Discussion/?cmd=GetPwdFile
now without sending any cookies. Maybe you can figure out why the server replies with a 404 instead of a 200 when run from the cloning process. Try a very simple elogd.cfg on your sever side, just the basic thing with a "Password file = ..." setting. Do you have any blanks in your logbook name? Are you using Apache as a proxy?
Anyhow, if this does not work for you, just copy your password file manually as you did already. The rest should then work fine for you.
- Stefan |