| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66355
|
Thu May 7 13:35:32 2009 |
 | Rich Sterling | rbsterli@juno.com | Question | All | 2.7.6 | Re: Office 2007 file attachments download as zip due to mime config |
| Stefan Ritt wrote: |
| Rich Sterling wrote: |
|
Are there any plans to add the new mime extensions to the elogd.c source? (Instead of forcing users to use FireFox or Right click, save-as and rename?
|
Ok, I added the MIME extensions in ELOG Rev. 2196. The forum runs already the updated version, so can you try with the demo attachments from your entry?
|
It looks good from here! Thanks!!
Best Regards,
Rich |
|
66357
|
Thu May 7 15:09:09 2009 |
 | Allen | bastss@rit.edu | Bug report | Linux | 2.7.6 | User can modify Fixed Attributes Edit when selecting preview |
Hi. I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.
I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields. When I click the edit button, everything looks restricted as it should be, but if I click Preview, the user is then able to change the fixed attributes.
Is there anyway to remove the preview button inside the edit page, or is anyone else having this issue?
Thanks,
Allen |
|
66361
|
Thu May 14 17:41:44 2009 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.6 | E-log crash |
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.
So this only happens when I am not observing the input formats or the mandatory fields.
This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.
Server listening on port 8079 ...
Program received signal SIGSEGV, Segmentation fault.
0x0000000000414077 in is_script (
at src/elogd.c:5414
5414 for (i = 0; script_tags[i][0]; i++) {
(gdb)
Soren |
|
66362
|
Thu May 14 17:59:04 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6 | Re: E-log crash |
| soren poulsen wrote: |
|
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.
So this only happens when I am not observing the input formats or the mandatory fields.
This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.
Server listening on port 8079 ...
Program received signal SIGSEGV, Segmentation fault.
0x0000000000414077 in is_script (
at src/elogd.c:5414
5414 for (i = 0; script_tags[i][0]; i++) {
(gdb)
Soren
|
It would be best if I could reproduce your problem. So can you start from a very simple configuration file, add your constraints until the problme happens, and then send me the config file? |
|
66364
|
Tue May 19 15:19:16 2009 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.6 | Re: E-log crash |
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.
So this only happens when I am not observing the input formats or the mandatory fields.
This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.
Server listening on port 8079 ...
Program received signal SIGSEGV, Segmentation fault.
0x0000000000414077 in is_script (
at src/elogd.c:5414
5414 for (i = 0; script_tags[i][0]; i++) {
(gdb)
Soren
|
It would be best if I could reproduce your problem. So can you start from a very simple configuration file, add your constraints until the problme happens, and then send me the config file?
|
Hi
The problem is not exactly what I thought, but I did track it down. Here is a logbook definition that reliably creates a segmentation fault in e-log. This logbook's only useful purpose is in fact to create a segmentation fault:
You select "New", then "Select", without entering anything.
--------------
Login user = Admin
Attributes = Link
Change Link = <a href="https://$Link"">$Link</a>
---------------
I would be able to create some more debugging information of course, if needed.
Regards
Soren
|
|
66370
|
Thu Jun 4 14:05:58 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6 | Re: E-log crash |
| soren poulsen wrote: |
|
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.
So this only happens when I am not observing the input formats or the mandatory fields.
This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.
Server listening on port 8079 ...
Program received signal SIGSEGV, Segmentation fault.
0x0000000000414077 in is_script (
at src/elogd.c:5414
5414 for (i = 0; script_tags[i][0]; i++) {
(gdb)
Soren
|
I had finally the same problem. This is due to a bug indeed inside is_script(). It has been fixed in revision 2201. |
|
66371
|
Thu Jun 4 14:37:54 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6 | Re: User can modify Fixed Attributes Edit when selecting preview |
| Allen wrote: |
|
Hi. I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.
I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields. When I click the edit button, everything looks restricted as it should be, but if I click Preview, the user is then able to change the fixed attributes.
Is there anyway to remove the preview button inside the edit page, or is anyone else having this issue?
|
Thanks for reporting this bug. I fixed it in revision #2203. |
|
66384
|
Sun Jun 7 06:29:55 2009 |
 | Gerardo Pruneda | gerardopruneda@yahoo.com | Question | Windows | 2.7.6 | I can not access the Logbook from another machine |
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable. |