| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68276
|
Mon Mar 7 13:03:13 2016 |
 | Juergen Diefenbach | diefenba@uni-mainz.de | Bug report | Linux | 3.1.1 | Re: Execute new|edit doesn't seem to work |
| Andreas Luedeke wrote: | I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
If that is the case then Stefan will know where to look 
Cheers
Andreas |
Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!
In principle I could live with this as I don't think I need to have drafts enabled.
Cheers,
Jürgen |
|
68277
|
Tue Mar 8 14:12:26 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.1 | Re: Execute new|edit doesn't seem to work |
| Juergen Diefenbach wrote: |
| Andreas Luedeke wrote: | I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
If that is the case then Stefan will know where to look
Cheers
Andreas |
Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!
In principle I could live with this as I don't think I need to have drafts enabled.
Cheers,
Jürgen |
I would speculate that "Execute new" is not executed, when a draft is saved (as one would expect, since it's only a draft), but is neither executed when a draft is submitted (not as one would expect).
Good that you're fine for the moment.
If you could add a minimal configuration to reproduce the problem, then Stefan would have it easier to debug it. |
|
68310
|
Thu Apr 28 22:38:00 2016 |
 | Adam Fairbrother | afairbrother@sd73.bc.ca | Bug report | Linux | V3.1.1-0767eb0 | Trouble with Find and Conditional attributes |
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources) |
|
68311
|
Thu Apr 28 22:54:08 2016 |
| Adam Fairbrother | afairbrother@sd73.bc.ca | Bug report | Linux | V3.1.1-0767eb0 | Re: Trouble with Find and Conditional attributes |
This may be due to how I have my config file setup
Example:
Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
| Adam Fairbrother wrote: |
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)
|
|
|
68314
|
Fri Apr 29 20:37:04 2016 |
| Adam Fairbrother | afairbrother@sd73.bc.ca | Bug report | Linux | V3.1.1-0767eb0 | Re: Trouble with Find and Conditional attributes |
Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.
This:
Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4
Still fails to set attribute B to a option list on the find page.
| Adam Fairbrother wrote: |
|
This may be due to how I have my config file setup
Example:
Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
| Adam Fairbrother wrote: |
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)
|
|
|
|
Draft
|
Tue May 31 19:53:59 2016 |
| S. Caiazza | caiazza@kph.uni-mainz.de | Bug report | Linux | 2.9.2 | Unable to set a custom logbook dir on Debian 8 from the repository package |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks a |
|
68323
|
Tue May 31 20:03:53 2016 |
| S. Caiazza | caiazza@kph.uni-mainz.de | Bug report | Linux | 2.9.2 | Unable to set a custom logbook dir on Debian 8 from the repository package |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there? |
|
68324
|
Fri Jun 3 08:16:31 2016 |
| Christian Ludwig | @ | Bug report | Linux | ELOG V3.0.0-21d | elogd dies upon search |
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text:
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
The only change we did was adding/editing entries.
Does anyone else encounter the same issue ?
I did not find any hint in release notes that this issue would be fixed in a later version
Please don't get me wrong, I am not complaining. Elog does a great job for us since years.
Christian |