ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1796
|
Wed Apr 5 20:25:42 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.1-1684 | Triggering $shell question | Should this work? rev1684 now allows $shell to pass attribute contents to the shell command and whenever a new entry is submitted or when one Edits/Replys the Subst is triggered, but I would like to be able to trigger this whenever a new value in the options pulldown is selected (assume Risk2 and Risk3 are identical to Risk1). Being able to trigger a regular Preset works fine (like {1} preset Date = $date ) but I would like to trigger the Subst. Maybe a better question, what actions (Subst, Preset, Change, Execute, etc.) I've tried Subst and Preset but not much luck.
##################################################
# Define Risk1
#
Options Risk1 = 10{30}, 20{31}, 30{32}, 40{33}, 50{34}, 60{35}, 70{36}, 80{37}, 90{38}, 100{39}
{30,31,32,33,34,35,36,37,38,39} Subst TotalRisk = $shell(gawk 'BEGIN{ print $Risk1 + $Risk2 + $Risk3 }' )
|
67736
|
Tue Jan 6 03:04:51 2015 |
| Banata | jogjacard@yahoo.com | Question | Windows | 3.0.0 | Translation problem | Hello, I try to translate elog using 2.9 version, I never try on 2.9 until new version 3.0 released
I translate 2 files here : elcode_indonesia.html and eloglang.indonesia,
after new version 3.0 I try to load those translation to the latest version using :
Language : indonesia
but language still in English, What I'm missing here?
|
66682
|
Wed Jan 13 12:00:04 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Topic changed to: emails sent/received after edited entries. | > > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry. The
> > > next email received was due to the third entry of this thread.
> >
> > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> >
> > 1st reply to your entry.
> >
> > 1st reply edited.
>
> I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem
> with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay
> between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML,
> your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more
> likely.
Hi Stefan,
I confirm that this is a slow internet line, so that explains the Proxy Error.
Maybe I should just keep my head down on threads where people use html coding ;-)
Did you receive two emails to my entry 66677? I only received one.
I only received one email to your posting 66680 - the first entry, not the edited version. |
66683
|
Wed Jan 13 12:18:54 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.7.8 | Topic changed to: emails sent/received after edited entries. | > > > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry. The
> > > > next email received was due to the third entry of this thread.
> > >
> > > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> > >
> > > 1st reply to your entry.
> > >
> > > 1st reply edited.
> >
> > I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem
> > with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay
> > between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML,
> > your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more
> > likely.
> Hi Stefan,
>
> I confirm that this is a slow internet line, so that explains the Proxy Error.
>
> Maybe I should just keep my head down on threads where people use html coding ;-)
>
> Did you receive two emails to my entry 66677? I only received one.
>
> I only received one email to your posting 66680 - the first entry, not the edited version.
I checked my email server and found that the second message really went though it. But then I realized that there is indeed the "Message-
ID:" in the email header (which I completely forgot in meantime). So maybe George Paplexis is right in that some mail
server/forwarder/receiver ignore a second email if it has the same ID. That would mean however that I have to introduce a "revision
number" for elog entries, which gets incremented on each edit and gets attached the the message-ID, so that it becomes unique again.
That's quite some work and has to wait a bit. |
66684
|
Wed Jan 13 12:27:32 2010 |
| David Pilgram | David.Pilgram@epost.org.uk | Info | Linux | 2.7.8 | Topic changed to: emails sent/received after edited entries. | > > > > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry. The
> > > > > next email received was due to the third entry of this thread.
> > > >
> > > > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> > > >
> > > > 1st reply to your entry.
> > > >
> > > > 1st reply edited.
> > >
> > > I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem
> > > with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay
> > > between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML,
> > > your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more
> > > likely.
> > Hi Stefan,
> >
> > I confirm that this is a slow internet line, so that explains the Proxy Error.
> >
> > Maybe I should just keep my head down on threads where people use html coding ;-)
> >
> > Did you receive two emails to my entry 66677? I only received one.
> >
> > I only received one email to your posting 66680 - the first entry, not the edited version.
>
> I checked my email server and found that the second message really went though it. But then I realized that there is indeed the "Message-
> ID:" in the email header (which I completely forgot in meantime). So maybe George Paplexis is right in that some mail
> server/forwarder/receiver ignore a second email if it has the same ID. That would mean however that I have to introduce a "revision
> number" for elog entries, which gets incremented on each edit and gets attached the the message-ID, so that it becomes unique again.
> That's quite some work and has to wait a bit.
I had come to the same conclusion about the mail header being the same (see my email to you for full details).
Sorry to all your subscribers for the email ping pong, although if others did receive two emails on the relivent entries - one original, and
one edited, it would be interesting, if possibly now academic, to know. |
66155
|
Tue Jan 20 15:09:54 2009 |
| Michael Ambrus | ambrmi09@gmail.com | Bug report | Windows | 2.7.5 | Top group causes: Internal error, no valid header! | Having "Top group" in a config-file for Windows will cause:
GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0
Internal error, no valid header!
Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin. |
1919
|
Thu Aug 31 21:46:15 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.2-1714 | Top Text and Bottom Text only show "text" --- no files | Just compiled 2.6.2-1714 and "Top text" and "Bottom text" interpret everything as "text" --- nothing is interpreted as a file to be included, unless there is a new syntax. |
1379
|
Fri Aug 5 02:27:15 2005 |
| Chris Green | greenc@fnal.gov | Bug report | Linux | 2.6.0-CVS | Top Groups, Show Top Groups, password file and Protect Selection page have nasty interaction | Hi,
Just as our ELOG went into production, I tripped over a couple of related (I think) bugs.
First, the easy one: line 21368 of src/elogd.c has a compile warning which looks non-benign. I fixed it in my local copy with:
Index: elogd.c
===================================================================
RCS file: /usr/local/cvsroot/elog/src/elogd.c,v
retrieving revision 1.739
diff -r1.739 elogd.c
21368,21369c21368
< sprintf(str, "?fail=1", user);
< redirect(lbs, str);
---
> redirect(lbs, "?fail=1");
Regardless (ie if I use the original CVS code or the patched version), a hard-to trace problem occurs with my configuration whereby users are denied access after password entry at the logbook selection page (even when details are verifiably correct), and users are dropped through to the next (non-protected) Top Group page. This problem goes away if "Protect Selection Page" is turned off.
A kind of "shadow" of this problem occurs if you create a new logbook from the Change Config File page, whereby after creating the new logbook one is dropped through to the next Top Group's selection page after saving the configuration (and the url has ?fail=1 added to it, althoguh line 21368 above is hardly the only place where this could have occurred).
I think all these things are linked. I'd be grateful if you could review this section of this code for possible causes of these problems. While we can operate for now with non-logged-in users able to see our list of logbooks, that is not something we want for the long term.
Thanks for your help,
Chris. |
|