| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68880
|
Fri Dec 21 14:59:05 2018 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.3 | Re: inactive users |
Thanks for the fix, I merged it into the current development branch.
Stefan |
|
68881
|
Wed Jan 9 11:43:48 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | 2.9.2-245 | Re: MIME-version header duplicated in e-mail messages. |
I just checked the current installatin, and just found one MIME-Version in the header, even with attachments:
MIME-Version: 1.0
--------------717E3059287C82F12BC14941
Content-Type: multipart/related;
boundary="------------4543EB0E5AAC14B461D70512"
No idea where your second header comes from, but sometimes I have seen some SPAM filters adding things to headers.
Stefan
| Michal Falowski wrote: |
|
When there are attachments in an entry, logbook is adding additional "MIME-Version" header to e-mail messages.
Spam filter in our university system is mostly giving warnings:
- X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
But sometimes it is not redirecting further the message.
- Remote Server returned '< #5.6.0 smtp; 554 5.6.0 Bounce, id=27666-07 - BAD HEADER>'
In code I noticed there is always "MIME-Version" header added to the message and additionaly it is added again when a file is attached. I think it is not neccessary to add again this header.
|
|
|
68885
|
Tue Feb 5 08:10:32 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.3 | Re: quick filter not working for attributes with special char |
No, there is no quick workaround. The only way is to go through your logbook files manually (or with a script), and replace all occurrences of that attribute.
Stefan |
|
68887
|
Fri Feb 8 14:57:05 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | v3.1.1 | Re: Images in notifications |
Your observation is correct. The mailer inside elog should scan all email bodies and replace all <img> tags correctly. I put that on my todo list.
Stefan
| Patrick Sizun wrote: |
|
Hello,
I am using Elog v3.1.1. When entries contain embedded images, these images are attached to the email notifications but are not properly displayed in the body of the email.
Is it expected?
For example, with an image file myimage.png the email source code contains <img alt="" height="150" src="190208_143305/myimage.png.png" width="200">
Maybe the email should make use of the Content-ID of the attached image?
|
|
|
68891
|
Wed Feb 20 15:14:32 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.14 | Re: Unwanted double entries eg. double clicking submit button |
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
68894
|
Wed Feb 20 22:41:23 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.14 | Re: Unwanted double entries eg. double clicking submit button |
"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately. Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research group, I only can devote this hour once in a while, depending on my work load. Sometime even the weekends are too short.
| Alan Grant wrote: |
|
I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?
Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.
Endless thanks for this product and all your work Stefan.
| Stefan Ritt wrote: |
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
|
|
68895
|
Wed Feb 20 22:45:39 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: New feature request for Options list |
I can put it on the wish list.
| Alan Grant wrote: |
|
Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the attributes in the Config file directly?
This would make it much easier to maintain a particular list that is referenced in several log books.
|
|
|
68899
|
Tue Feb 26 14:31:00 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: Migration from 3.1.2 version to 3.1.4 |
To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the new server. If the URL of the server changes, you have to adjust it in elogd.cfg.
Stefan
| Vladimir Travalja wrote: |
|
Hi,
sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4
Is the migration from one system to another possible? What are the prerequisites for migration?
Are there any instructions how to do it?
Thank you in advance and have yourself a lovely day,
Warmest regards
|
|