Problem with autosave functionality when combined with no 'edit' button, posted by Thomas Lindner on Tue May 5 07:33:50 2015
|
We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.
Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages. So we have (up to
now), had the following set of commands specified in elogd.ccfg |
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 11:01:36 2015
|
Hi Thomas,
just my two cent: as a quick workaround (for now) you could restrict editing messages to a short time range, like 30 minutes. That would cover
most cases of draft messages.
Restrict edit time = 0.5
But I agree that |
|
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Stefan Ritt on Tue May 5 12:09:53 2015
|
Arghhhh! Guess how many people asked me for the autosave feature! I worked really hard on it (including an airplane flight to Japan!), not the next guy
comes "can we disable that feature?". |
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Andreas Luedeke on Tue May 5 12:17:24 2015
|
| Oups, now I feel almost a little bit sorry for asking But thank you anyway!!! |
|
Re: Problem with autosave functionality when combined with no 'edit' button, posted by Stefan Ritt on Tue May 5 12:05:47 2015
|
I changed the code such that editing of draft messages is always possible, even if the "edit" command is not allowed otherwise. Update is in
GIT. Please check if that works at ND280.
Thomas |
Load attribute options from attributes in another logbook, posted by Francois Cloutier on Mon May 4 22:28:37 2015
|
Hi again,
Hope I'm not draining to much time from you guys !
|
|
Re: Load attribute options from attributes in another logbook, posted by Andreas Luedeke on Tue May 5 10:54:54 2015
|
> Hi again,
> Hope I'm not draining to much time from you guys !
>
|
|
Subst Attributes..., posted by Francois Cloutier on Fri May 1 21:19:18 2015
|
Good day,
I'm new to Elog and I find it really nice and straight foward...
I still have a few questions that I couldn't address reading the manuals. |
|
Re: Subst Attributes..., posted by Andreas Luedeke on Mon May 4 13:23:55 2015
|
Hi Francois,
welcome to the community! I'll try to answer your questions inline (Numbering them would have been a good idea ;-):
-
I'm creating a logbook with a lot of attributes. I would like to know if there is a way to name (display) my attribute differently then it's original
name. That way I could program $attrib1; $attrib2, etc, and map a name to display the column accordingly... Is it something possible ? |
|
Re: Subst Attributes..., posted by David Pilgram on Mon May 4 14:10:08 2015
|
Hi Francois and Andreas,
On Francois' first question, I wonder if Francois is using attrib1, attrib2... as the actual attribute names in the config file. If
this is the case, Francois, you can name attributes with suitable names in the configuration file and dictate which ones appear in the List and Threaded |
|
Re: Subst Attributes..., posted by David Pilgram on Mon May 4 15:13:08 2015
|
I only saw Andreas' edited version of the original enquiry, so I didn't see the orignal config file under discussion - so most of my previous
entry is totally pointless. Sorry about that.
David |
|
Re: Subst Attributes..., posted by Stefan Ritt on Mon May 4 15:44:07 2015
|
Indeed there was a bug when you have "Show Text = 0". I fixed that in the current GIT version. I also hide the "Preview" button if
"Show text = 0" since it really makes no sense there. I made a Windows Patch 3.1.0-3 which
ontains this fix. |
Re: Subst Attributes..., posted by Francois Cloutier on Mon May 4 16:03:19 2015
|
Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!
Thanks alot Stefan, I will try it right away !!
|
|
Re: Subst Attributes..., posted by Andreas Luedeke on Tue May 5 09:22:23 2015
|
> Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!
>
> Thanks alot Stefan, I will try it right away !!
|
|
elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015
|
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
|
|
Re: elogd lost entry database without restart during file system trouble, posted by Stefan Ritt on Thu Apr 30 13:01:29 2015
|
First, I can only fix problems which are reproducible. Can we do another power outage at PSI again?
But seriously, I guess what happened is that elog sees an empty directory when the AFS server
|
|
Odd behaviour when attaching a file to an entry, posted by David Pilgram on Sun Apr 12 21:12:29 2015
|
Having installed v3.1.0 on a test logbook, I find that I can browse and select a file, but when I click on the "Upload" button, I get a pop-up
message from the browser asking me:
"This page is asking you to confirm that you want to leave - data you have entered may not be saved." |
|
Re: Odd behaviour when attaching a file to an entry, posted by Stefan Ritt on Thu Apr 23 15:13:06 2015
|
This problem has been fixed in Version 3.1.0-2. Please upgrade.
David
Pilgram wrote:
Having installed v3.1.0 on a test logbook, I find that I can browse |
|
Re: Odd behaviour when attaching a file to an entry, posted by David Pilgram on Thu Apr 23 15:37:37 2015
|
Thanks Stefan, that did the trick.
Had a bit of an effort with the git repository, though, kept getting 403 errors when tried the
git clone https://bitbucket.org/ritt/elog as per the "download" page. |
|
Max Logbooks for Email notify, posted by Oliver Kleinau on Wed Apr 8 11:40:27 2015
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the
changes the rest of the entrys are cut off. |
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 08:37:19 2015
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
Oliver
Kleinau wrote:
Hi, |
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 09:59:42 2015
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!! |
|
Re: Max Logbooks for Email notify, posted by Stefan Ritt on Wed Apr 22 13:40:19 2015
|
Ok, I fixed this in the current GIT version. You might check if that works for you.
Oliver
Kleinau wrote:
It was str variable in function process_http_request in elogd.c. |
ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Thu Apr 2 15:44:33 2015
|
This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments,
it contains a long awaited "autosave" feature.
Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). |
|
Re: ELOG Version 3.1.0 announcement, posted by Banata Wachid Ridwan on Wed Apr 15 04:02:41 2015
|
congrats, any detail changelog? I assume in software packages?
is it save just install and overwrite the old version?
Stefan |
|
Re: ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Wed Apr 15 09:01:04 2015
|
The changelog is here: http://midas.psi.ch/elog/download/ChangeLog
It is save to install the new version over the old one.
|
Strange browser behaviour with chrome?, posted by Tim Schel on Mon Mar 30 14:46:28 2015 
|
Hello there,
I have been using ELOG for 4 years now and all of a sudden I see a strange behaviour.
|
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Mon Mar 30 17:48:06 2015
|
The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015
|
[quote="Stefan Ritt"]The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
|
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Tue Mar 31 11:44:27 2015
|
[quote="Andreas Luedeke"]the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry,
then the display after that entry may be spoiled.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font>
in your entry, then the display after that entry may be spoiled.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Wed Apr 1 11:41:31 2015
|
[quote="Andreas Luedeke"]If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:31:28 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't
it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:39:14 2015
|
Proof of principle ;-) |
|
Re: Strange browser behaviour with chrome? </table>, posted by Stefan Ritt on Wed Apr 1 20:25:21 2015
|
[quote="Andreas Luedeke"]Now I'm confused: if I create an entry with "elog -n 2 ...", then I put HTML code into elog and it is displayed as HTML. This HTML
code does NOT convert a "<" into "<", otherwise you could not display any HTML.
But of course this code can be wrongly formatted, for example it can contain a </table> tag without a <table> tag before it. This will definitely spoil |
|
Re: Strange browser behaviour with chrome?, posted by Tim Schelfhout on Wed Apr 1 11:01:14 2015
|
Thank you all of you for your notes ...
Anyway I have no time at the present to debug this ... at the level of configuration file.
I discovered however that the Incognito Mode of Chrome does NOT seem to have this problem??
|