| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69589
|
Fri Dec 2 14:12:35 2022 |
 | Laurent Jean-Rigaud | lollspam@free.fr | Bug fix | Linux | 3.14 git | Buildrpm / copy .cxx in place of .c | Hi Stefan,
It seems buildrpm should be updated to take care of cpp files. Plz replace "cp <blahblah>.c ..." by "cp <blahblah>.cxx ..." .
Also, uncomment the hostname test witch activates all authentification options by default. It should be done by adding options as follow : buildrpm ver rel -ldap -ker ...
By default, i can not build elog with LDAP.
After that mods, rpms are builded under EL7 (w/o LDAP support which is not useful for me).
Bye
Laurent |
|
67155
|
Fri Dec 16 18:28:58 2011 |
 | Hung Dao | hungtdao@yahoo.com | Question | Windows | 2.9 | Build with Visual Studio 2010? | First I have tried to checkout the source code and got an error shown in below. So, I clicked on the Web Access link to download the trunk.tar.gz. I have opened elogd.sln in Visual Studio 2010. Despite of downloading openssl and and installing krb5, I still received errors related to header files that could not be opened or found. Has anyone checked out all files from trunk.tar.gz and built successfully. Any hint or advise prior to build this elogd solution in VS2010 will be highly appreciated.
>svn checkout svn+ssh://svn@savannah.psi.ch/repos/meg/elog/trunk elog
svn: E720002: Unable to connect to a repository at URL 'svn+ssh://svn@savannah.psi.ch/repo
s/meg/elog/trunk'
svn: E720002: Can't create tunnel: The system cannot find the file specified.
|
|
275
|
Wed Apr 9 13:49:32 2003 |
 | nickc1 | nick@nick.com | Info | | | Bugs with 2.3.5 | Forgot password option generates an error message
Password file hashes are different causing migrated password files to fail
but only for certain users, try password 516135 hashed in 2.3.4 and compare
to version 2.3.5 they are different.
Summary page title = string doesnt work also it results in the default ELOG
DB Name
HELP |
|
617
|
Thu Jul 22 16:50:19 2004 |
| Todd Corsa | tcorsa@bnl.gov | Bug report | Linux | 2.5.3 | Bugs in newer updates w/ Debian install? | 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. I find that if I
allow fewer quick filter options it seems to work more consistently. For
example:
Example 1-
Quick filter = Date
The date filter will work without a problem no matter how many times I use
it.
Example 2-
Quick filter = Date, Category, Status, Priority
The first filter I use will work, but upon trying a new filter, or just a
new option in the same filter, all options return to "All Entries" and no
filter options have any effect on the view.
If I exit the log book, and come back in, it works for the first filter
attempt, then stops again.
This used to work fine prior to the update. I should also mention that the
original installation of ELOG was from the Debian package. At that point,
nothing was where the documentation said it should be (e.g. elogd.cfg was
called elog.conf and was placed in the /etc/ directory). Everything worked
fine, so I left it alone. When I recompiled with the newer elogd.c,
anything that required a path was hosed, so I now have to specify the
resource directory and the path to the conf file when starting ELOG. I
don't know why this would affect the Quick Filter, and I'd assume that it
would just stop working all together. Also, when I recompiled using "gcc -
O -o elogd elogd.c", I received the following warning:
elogd.c:546: warning: conflicting types for built-in function `logf'
Any suggestions?
Thanks!
Todd |
|
2033
|
Thu Nov 2 18:02:44 2006 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Bug? Password file location changed | 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 |
|
69363
|
Tue May 4 14:45:47 2021 |
| Faith | faithlessangel85@gmail.com | Bug report | Linux | 3.1.2 | Bug: "Append on edit" triggers too often | 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. |
|
68667
|
Mon Aug 21 11:45:06 2017 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 3.1.3-aded4ae | Bug with Drafts and Language German | 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"); |
| Attachment 1: elog_lang_pending_draft_bug.png
|
|
|
69224
|
Tue Sep 22 18:54:04 2020 |
| Andrey | kowaraj4stuff@gmail.com | Bug report | Linux | ELOG V3.1.4-493 | Bug report. "Submit" button misbehave | Hi.
I am an IT guy of the AMS collaboration at CERN. We have been using your wonderful elog software for about 10 years now. Thanks! It served us so well that I guess we never got in touch with you.
Recently we have upgraded it (probably for the first time in years) up to the version ELOG V3.1.4-4936b76.
Since then, we have a particular problem. And finally, I managed to reproduce it.
So, when I edit a record and click the "Submit" button it goes back to the summary view (as usual, as before) but it does not really save the entry. And it shows that the record is still being edited. I can actually click "back" in the browser and not to lose the modifications (otherwise, if I try to edit and steal the lock, it's lost).
I will try to figure out where the problem is coming from. The most verbose mode of the elog server I've found is just GET-POST lines, not helpful. Is there a debug mode?
Also, we ran httpd configured with the elogd as a virtual host (proxy).
Any help is very appreciated.
Cheers,
Andrey
|
|