ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66505
|
Mon Aug 10 21:19:50 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | I've just noticed that it has also sorted another Option, which are selected as radio buttons. Again, this is a
list which has a natural - again, in this case, chronological - order.
Because of this, I'm going to have to turn off this feature as it is on my system. I hope something can be sorted
on this.
> (For some reason I could not add this in Dennis's thread.)
>
> I like this new feature, BUT
>
> I happen to have two Options: Options System, and Options Status.
>
> System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> this is made up)
>
> Options System: 3.1, NT, 2000, XP, Vista
>
> where the natural order here is chronological.
>
> Perhaps the configuration file option could be more specific, for example
>
> Sort attribute Options Status = 1
>
> which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> the original syntax which defaults to sort *all* Options. |
66504
|
Mon Aug 10 21:07:15 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | Linux | 2.7.7-2251 | Comment on: Alphabetize Quick Option filter | (For some reason I could not add this in Dennis's thread.)
I like this new feature, BUT
I happen to have two Options: Options System, and Options Status.
System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
this is made up)
Options System: 3.1, NT, 2000, XP, Vista
where the natural order here is chronological.
Perhaps the configuration file option could be more specific, for example
Sort attribute Options Status = 1
which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
the original syntax which defaults to sort *all* Options. |
66503
|
Mon Aug 10 17:14:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.7.6 | Re: alphabetize Quick Filter items? |
Dennis Seitz wrote: |
Stefan Ritt wrote: |
Dennis Seitz wrote: |
Hi Stefan,
I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.
We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.
I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?
Thanks again for a *very* useful logging system!
Dennis
|
The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items
Options Type = C, D, A, B
they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like
Options Type = A, B, C, D
I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.
- Stefan
|
Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!
|
Ok, I implemented
Sort attribute options = 1
in the current SVN revision. |
66502
|
Fri Aug 7 23:09:42 2009 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.6 | Re: alphabetize Quick Filter items? |
Stefan Ritt wrote: |
Dennis Seitz wrote: |
Hi Stefan,
I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.
We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.
I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?
Thanks again for a *very* useful logging system!
Dennis
|
The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items
Options Type = C, D, A, B
they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like
Options Type = A, B, C, D
I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.
- Stefan
|
Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!
|
66501
|
Fri Aug 7 08:36:19 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.3 | Re: Pre-populate Attachments in URL |
That would be nice, I want this, too! But unfortunately your browser does not allow this for security reasons, and I found no way around. Assume you look to a page on the internet, and it pre-populates a file selector with something like /etc/passwd or any other sensitive file. Then this box gets hidden by some CSS style so you don't see it. So as soon as you click on something on that page, your sensitive files gets submitted, and you don't want that. Therefore it's impossible to pre-populate file selector boxes.
- Stefan |
66500
|
Thu Aug 6 22:29:12 2009 |
| Erik Iverson | eiverson@ornl.gov | Question | All | 2.7.3 | Pre-populate Attachments in URL | Is there a way to pre-populate the new entry window with one or more attachments? Per the documentation, this is easy to do with attributes, i.e., http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Info as a URL or bookmark will do it. I'd like to do the same thing with attachments, for example http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Photograph&attfile1=picture1.jpg&attfile2=picture2.jpg might prepopulate two attachments, giving me an edit window all ready to enter the brief description represented by the two pictures. |
66499
|
Thu Aug 6 13:09:50 2009 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.7 | Re: HTML in attribute values |
Stefan Ritt wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using syntax like (from the doc):
Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>
Until yesterday this was interpreted as HTML.
After upgrading to 2.7.7, I still get a valid link but the full HTML code is also displayed: the user sees
''<a href="http://any.company.com/telbook.cgi?search=myname">myname's telephone number</a>''
where he should only see:
''myname's telephone number''
I am 99% sure this is a consequence of the upgrade. Is there a way to get the original behaviour back?
Thanks a lot
Soren Poulsen
|
I have more precise information about the nature of this issue, which concerns the display of E-logs
In the previous version 2.7.6, E-log would generate HTML like this:
td class="attribvalue">
<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15403690&button=Search">15403690</a> </td>
In the latest version 2.7.7, E-log generates HTML like this (for the same attribute):
<td class="attribvalue">
<a href="<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search">https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search</a>">15575045</a> </td>
|
You need
Allow HTML = 1
in your configuration file. See the documentation for details. This featue is new in 2.7.7.
|
Thanks a lot. In fact I did not read the 2.7.7 version of the documentation, which I should have done.
Have a good aftenoon
Soren
|
66498
|
Thu Aug 6 12:11:50 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7 | Re: HTML in attribute values |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using syntax like (from the doc):
Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>
Until yesterday this was interpreted as HTML.
After upgrading to 2.7.7, I still get a valid link but the full HTML code is also displayed: the user sees
''<a href="http://any.company.com/telbook.cgi?search=myname">myname's telephone number</a>''
where he should only see:
''myname's telephone number''
I am 99% sure this is a consequence of the upgrade. Is there a way to get the original behaviour back?
Thanks a lot
Soren Poulsen
|
I have more precise information about the nature of this issue, which concerns the display of E-logs
In the previous version 2.7.6, E-log would generate HTML like this:
td class="attribvalue">
<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15403690&button=Search">15403690</a> </td>
In the latest version 2.7.7, E-log generates HTML like this (for the same attribute):
<td class="attribvalue">
<a href="<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search">https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search</a>">15575045</a> </td>
|
You need
Allow HTML = 1
in your configuration file. See the documentation for details. This featue is new in 2.7.7. |
|