Links to images in notification message, posted by Devin Bougie on Fri Feb 26 17:20:52 2016 
|
We see two problems with the notificaiton email when attaching an image inline using drag-and-drop.
- The thumbnail does not appear in its proper location inline. There is a ? placeholder where the thumbnail should be, and the thumbnail then appears at the end of the message.
- Neither the ? placeholder nor the thumbnail that do appear are clickable.
Our v2.9.2 test installation exhibits the desired behavior.
- The thumbnail appears in its correct location inline.
- If you click on the thumbnail, you arrive at a URL displaying the full size image.
I am not able to drag-and-drop into the body of this message to test the behavior here. I am attaching a screenshot showing an example of the problem from our server.
Any suggestions would be greatly appreciated.
Many thanks,
Devin
|
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. 
What I did so far to understand what goes wrong is I looked into elogd.c and found invoid submit_elog(LOGBOOK * lbs) that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).
When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
Re: Links to images in notification message, posted by Devin Bougie on Fri Feb 26 18:11:14 2016
|
From the notification I received, it looks like "2" is a problem with this server. In the email notification, we would like images to be a link to a URL displaying the full-size image (as they are in v2.9.2).
Thanks,
Devin |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016
|
| Juergen Diefenbach wrote: | I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected.
[...]
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
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 |
|
Re: Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Mon Mar 7 13:03:13 2016
|
| 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 |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016
|
| 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. |
|
Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:38:00 2016
|
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) |
|
Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:54:08 2016
|
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)
|
|