| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66691
|
Mon Jan 18 02:14:01 2010 |
 | Gabriele Sirri | sirri@bo.infn.it | Question | Windows | 2.7.8-2283 | Re: quick filter |
| Stefan Ritt wrote: |
|
| deletoille wrote: |
|
| Stefan Ritt wrote: |
|
| deletoille wrote: |
|
Hello,
We would like to use more the quick filter command on attributes.
On the other hand, when we use it, the result does not displaying entries which are in answer of another attribute. Is there a command which allow that possibility like when we select display full entries in the search mode?
Thanks in advance
Xavier
|
I don't understand your questions. Can you please give an example.
|
Sorry for my english. In fact, i found the answer by myself. But I ll explain to you.
in attachement 1, a small part of our ELOG. When I choose FBT in the quick filter "groupe incriminé". Elog respond that there is no entrie found (attachement 2)
But, with the find function, when i select display full entries and FBT in "groupe incriminé", Elog show the entrie ( attachement 3).
I found the answer. In fact, Elog respond no entrie when threaded is selected. I have to choose Full or summary for that working.
sorry
Xavier
|
Actually what you report is a bug. The filtering does not work in threaded display mode, only in summary and full. I fixed that bug in the current SVN version, so if you download and compile it, you can give it a try. The fix will be contained in the next official release.
|
Hello,
I gave it a try. See: https://midas.psi.ch/elogs/Forum/66690
Gabriele
|
|
66692
|
Mon Jan 18 08:18:48 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.8-2283 | Re: Collapse to Last and Quick Filter | > However (considering the bug fixed for the collapsed thread display), breaking the thread is not a confortable solution.
Well, but it's the only way which gives you a 1:1 correlation between what you filter and what you see below. If you want to
see the full thread for an entry which gets shown after you apply a filter, just click on that entry, and you will be taken to
the single entry display which shows the full thread on top of it. This is the only way I can keep search results consistent,
so I would rather like to keep it like this. |
|
66711
|
Wed Feb 17 17:02:38 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Problem using attribute type | Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
|
66712
|
Thu Feb 18 13:21:15 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
| soren poulsen wrote: |
|
Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"
It was a mistake not to include the "global" settings in this bug report.
What probably happens is that something in the French translation (accents ?) disturbs the java scripting.
Soren
|
|
66713
|
Thu Feb 18 15:37:07 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"
It was a mistake not to include the "global" settings in this bug report.
What probably happens is that something in the French translation (accents ?) disturbs the java scripting.
Soren
|
To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.
Soren |
|
66726
|
Tue Mar 2 14:21:46 2010 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.8-2282 | Thread view problem in searches | Hi,
When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).
On the forum site I also note that the thread view is not indented when performing searches.
Does anyone have an idea ?
Soren
|
|
66733
|
Sat Mar 6 20:53:25 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
|
soren poulsen wrote:
|
|
Hi,
When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).
On the forum site I also note that the thread view is not indented when performing searches.
Does anyone have an idea ?
Soren
|
This seems to be a bug. I reproduced it with a different browser (Opera) with the default ELOG configuration. When I do Find and select Display Threads I have the message icons but the layout is not correct. Also, all message icons are of the "reply" type even if they are new threads.
This concerns only the latest build 2282.
Soren
|
|
66743
|
Thu Mar 11 15:44:01 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.8-2282 | Re: Thread view problem in searches |
| soren poulsen wrote: |
|
|
soren poulsen wrote:
|
|
Hi,
When I upgrade from build 2278 to 2282 the thread view changes when performing searches: The thread children are not indented and there are no "thread icons" in the search list (e.g. like the read right arrow for replies).
On the forum site I also note that the thread view is not indented when performing searches.
Does anyone have an idea ?
Soren
|
This seems to be a bug. I reproduced it with a different browser (Opera) with the default ELOG configuration. When I do Find and select Display Threads I have the message icons but the layout is not correct. Also, all message icons are of the "reply" type even if they are new threads.
This concerns only the latest build 2282.
Soren
|
That's not a bug, that's a feature 
But honestly, this feature was requested recently and implemented. See https://midas.psi.ch/elogs/Forum/66670. So when searching, the thread organization is broken up and messages are treated independently. If you want to see the thread for a certain entry in you search result page, click on that entry and you will see the full thread above the entry. |
|