Re: ELCode how to with URL, posted by toumbi on Tue Sep 11 11:36:04 2007
|
Thank you a lot !! |
|
Re: ELCode, posted by Stefan Ritt on Wed Oct 25 19:44:11 2006
|
| Alexandre Lindote wrote: | | can you think of any obvious reason why the ELCode would not work in the logbooks I set up? |
There is a good reason why this forum contains a ELOG Version tag which you are supposed to fill out for new entries. Without knowing which version you are using I cannot help you. Probably you have an old version which does not support the Allowed encoding. |
|
Re: ELCode, posted by Alexandre Lindote on Wed Oct 25 21:52:13 2006
|
| Stefan Ritt wrote: |
| Alexandre Lindote wrote: | | can you think of any obvious reason why the ELCode would not work in the logbooks I set up? |
There is a good reason why this forum contains a ELOG Version tag which you are supposed to fill out for new entries. Without knowing which version you are using I cannot help you. Probably you have an old version which does not support the Allowed encoding. |
Sorry about that... it's 2.6.2-1699, so a very recent one. |
|
Re: ELCode, posted by Alexandre Lindote on Fri Oct 27 13:02:50 2006
|
| Alexandre Lindote wrote: | Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
Ok, I think I found the problem... For some reason the elcode.js file was only in /usr/local/elog/scripts, but it was supposed to be in
/usr/local/elog/themes/default/ as well.
Creating a symlink between the two solved that problem. I can now do most things with the ELCode, but inserting images is still failing. I get this message from the firefox javascript console:
text.value has no properties (line 32 of elcode.js)
Any thoughts?
Alex |
|
Re: ELCode, posted by Stefan Ritt on Thu Nov 9 21:03:03 2006
|
| Alexandre Lindote wrote: |
| Alexandre Lindote wrote: | Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
Ok, I think I found the problem... For some reason the elcode.js file was only in /usr/local/elog/scripts, but it was supposed to be in
/usr/local/elog/themes/default/ as well.
Creating a symlink between the two solved that problem. I can now do most things with the ELCode, but inserting images is still failing. I get this message from the firefox javascript console:
text.value has no properties (line 32 of elcode.js)
Any thoughts?
Alex |
That's really strange. In the forum (http://midas.psi.ch/elogs/Forum), I have the elcode.js only in /usr/local/elog/scripts, and it works as you can try out yourself. Getting your javascript error might indicate that you have an old version of elcode.js combined with a newer executable of elogd. Try to update it. |
|
Re: E-log crash, posted by Stefan Ritt on Thu May 14 17:59:04 2009
|
| 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? |
|
Re: E-log crash, posted by soren poulsen on Tue May 19 15:19:16 2009
|
| 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
|
|
Re: E-log crash, posted by Stefan Ritt on Thu Jun 4 14:05:58 2009
|
| 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. |