Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Fri Apr 29 20:37:04 2016
|
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)
|
|
|
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 19:53:59 2016
|
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 |
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 20:03:53 2016
|
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? |
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
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 |
solved: elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:59:49 2016
|
I would like to share my findings about the solution of our problem:
One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.
So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment.
Since then, no more crash of elogs.
May this contribution be useful to other elog users...
Christian
Christian Ludwig wrote: |
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
|
|
pdf thumbnails in latest Imagemagick, posted by John Haggerty on Mon Jun 6 05:45:57 2016
|
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed. |
pdf thumbnails in latest Imagemagick, posted by John Haggerty on Mon Jun 6 05:51:44 2016
|
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed. |
Self register = 0 not working , , posted by rudy on Wed Jun 8 15:00:47 2016
|
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01 |