Re: Bugs in newer updates w/ Debian install?, posted by Todd Corsa on Wed Jul 28 22:12:03 2004
|
> > I just updated ELOG using the latest elogd.c, and now my Quick Filters seem
> > to stop working after the first or second filter attempt.
>
> Can you try if you can reproduce the problem with the current version? I tried
> your settings and could not reproduce it. I remember that I fixed some problems
> with quick filters, but that was some time ago (Apr 04). If the problem
> persists, can you send me your exact elogd.cfg?
Recai Oktas replied to me and let me know that I needed to use dpkg to create the
new Debian package instead of manually compiling it. I reverted to the original
Debian package to get everything running normally again, but I haven't had a
chance to try the upgrade again. As soon as I went back to the original elogd
everything worked fine (no changes to the elog.cfg required). I'm assuming that
the problem came from attempting to recompile a Debian package install manually.
Sorry for the bug scare!
Todd |
|
Re: Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:10:07 2006
|
| David Spindler wrote: | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
|
Re: Bug? Password file location changed, posted by Steve Jones on Thu Nov 2 23:17:10 2006
|
| David Spindler wrote: |
| David Spindler wrote: | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
| Quote: | The relocation was a documented change that Stefan made intentionally. Yes, it caught me too  |
|
|
Re: Bug? Password file location changed, posted by David Spindler on Fri Nov 3 14:40:36 2006
|
| Steve Jones wrote: |
| David Spindler wrote: |
| David Spindler wrote: | I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.
I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.
I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.
Thanks, keep up the great work, Stefan. You have a great program.
David Spindler |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
| Quote: | | The relocation was a documented change that Stefan made intentionally. Yes, it caught me too |
|
Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks! |
|
Re: Bug? Password file location changed, posted by Stefan Ritt on Tue Nov 7 09:22:52 2006
|
| David Spindler wrote: | | Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks! |
That change was actually made in SVN revision 1708 on Aug. 1st, 2006, which was after the release of 2.6.2. So it will be made official in 2.6.3 and documented accordingly. |
|
Re: Bug: "Append on edit" triggers too often, posted by Sebastian Schenk on Tue May 4 15:24:56 2021
|
I can confirm the issue also for "prepend on edit".
To be more precise, it gets executed everytime the condition state changes, if placed in the config without condition, or if placed in a condition, everytime the condition gets activated.
| Faith wrote: |
|
The command "Append on edit = " is getting executed everytime, when a dropdown menu is changed. This happens even at the first creation of an entry, so the append text stucks up multiple times in the text body.
|
|
|
Re: Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 12:16:05 2017
|
I've quickly checked: there are a couple more commands in the source code that are not language encoded. I guess some of them needs correction.
> egrep -n "cmd=[A-Za-z]" elogd.c
10293: rsprintf(" r.open('GET', '?jcmd=Unlock&edit_id=%d', true);\n", message_id);
11784: ("<label for=\"ELCode\"><a target=\"_blank\" href=\"?cmd=HelpELCode\">ELCode</a> </label>\n");
13663: "\r\n%s URL : %s?cmd=Config&cfg_user=%s&unm=%s\r\n", loc("Logbook"),
14562: redirect(lbs, "?cmd=Config");
14625: sprintf(str, "../%s/?cmd=Config", getparam("lbname"));
14678: sprintf(str, "../%s/?cmd=Config", lbn);
15703: combine_url(lbs, host, "?cmd=GetMD5", url, sizeof(url), &ssl);
16378: strcat(str, "?cmd=GetConfig"); // request complete config file
16380: strcat(str, "?cmd=Download"); // request config section of logbook
16570: strcat(str, "?cmd=GetPwdFile"); // request password file
17575: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17577: rsprintf("<br><b><a href=\"%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17579: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
18959: if (strstr(ref, "cmd=Search&"))
18960: strlcpy(strstr(ref, "cmd=Search&"), strstr(ref, "cmd=Search&") + 11, sizeof(str));
26728: rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
| Andreas Luedeke wrote: |
|
Hi Stefan,
when one creates a new entry, and a draft entry exists for the logbook, then a menu appears (see attachment).
If one select "Neuen Eintrag anlegen" then it should ignore the draft and create a new entry.
This feat is done by adding a "&ignore=1" to the "new" command: "<URL>/?cmd=New&ignore=1".
The problem is, that it should not be "cmd=New&..." but "cmd=Neu", since the commands are part of the translation.
Due to this, no new entry can be created as long as a draft exists; at least not in any language other than english.
This problem apparently existed since the beginning of drafts, but it only created problems at our site recently.
Kind Regards
Andreas
PS: Here's a patch that works:
diff elogd.c elogd.c-orig
9575,9576c9575,9576
< rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='?cmd=%s&ignore=1';\">\n", loc("Create new entry"),
< loc("New"));
---
> rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='%s';\">\n", loc("Create new entry"),
> "?cmd=New&ignore=1");
|
|
|
Re: Bug Found, posted by Stefan Ritt on Tue Jun 17 12:52:34 2003
|
> Correct Way prior to 2.3.8
>
> http://192.168.0.1:99/Provisioning%20Request/35
>
> Broken way with new version
>
> http://192.168.0.1:99/Provisioning Request/35
Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be
that you mixed up these two versions? To be precise, the fix happend in
Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a
version of elogd after that modification? I tried to reproduce your problem
with the official 2.3.8 version, but I got the correct result. |
|