Hi,
I have defined a quick filter based on an icon attribute and it does not work: no result. I have defined something like your "forum elog" (with Icon comment ): in the quick filter, i see the comments (that a good thing) but whatever i'm selecting, i have no entry.
Is it a bug or i miss something in the configuration ?
Regards
ELOG is a really helpful application 
Thanks a lot !! |
Stefan Ritt wrote: |
Franck C wrote: |
Hi,
I have defined a quick filter based on an icon attribute and it does not work: no result. I have defined something like your "forum elog" (with Icon comment ): in the quick filter, i see the comments (that a good thing) but whatever i'm selecting, i have no entry.
Is it a bug or i miss something in the configuration ?
|
I tried to reproduce your problem, but it worked fine for me. I used in elog.cfg:
[demo]
Attributes = Icon, Author, Type, Last Edit, Subject
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Quick filter = Icon
Then I entered two entries with different icons, and I selected the quick filter. It correctly showed me the entry with the icon I selected:

|
Yes you're right, but i want to see the comment in the quickfilter list, not the name of the icon :
[MyLogBook]
List Display = Auteur, Destinataire, Etat, Réponse, Rapport
Attributes = Auteur, Destinataire, Etat, Réponse, Rapport
IOptions Etat = icon3.gif, icon13.gif, icon14.gif, icon2.gif
Icon comment icon3.gif = Suggestion
Icon comment icon13.gif = Réfusée
Icon comment icon14.gif = Retenue
Icon comment icon2.gif = Réportée
Quick filter = Auteur, Date, Etat, Destinataire
All the entries:

When i'm selecting the quickfilter, it should display the entry "arthur":

|
> > I trust Stefan is reading this thread and will do something about it. My vote would
> > be to remove the download link to the windows executables and ask Debian to remove
> > the elog package. I think they have a way for upstream developers (Stefan) to request
> > removal of unmaintained out-of-date insecure versions of their stuff. ROOT
> > was in the same situation years ago, the Debian package for ROOT was very old version,
> > also built incorrectly, and everybody complained to us that our stuff does
> > not work (midas, rootana, etc).
>
> Yeah, I have to recompile the Windows version. Unfortunately my old Windows PC is gone, I
> switched now completely to MacOSX and Linux. Probably have to borrow something from somewhere.
> If anybody can compile the Windows version with the current source code I would be happy.
it would be good if the current state was listed in https://elog.psi.ch/elogs/Vulnerabilities/
It seems there's now updated builds for at least windows, and the debian package still outdated?
Personally, I don't think removing download links and pulling packages should be more than a temporary measure.
Treating people fairly IMHO means they should be able to reach a safe version by the same means that brought and left them exposed.
A clear central source would be best, one that has
- package autobuilds
- source
- cve list
If I understand correctly, currently only the source is up to date?
(I found py_elog on Github, so it could be an easy option to mirror ELOG there and let some free service handle the autobuilds.
I don't know how well one can flag vulnerabilities there, but likely it's possible, and ideally more people would help there.)
p.s.: My hat is off to the sysadmin who checked carefully, I wanted to introduce ELOG in a windows-centric place and I can't swear I would have checked this (official) download as well. |