ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 618 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6454 Entries

Goto page Previous 1, 2, 3 ... 617, 618, 619 ... 805, 806, 807 Next

Thu Jan 12 16:06:16 2006

Re: Thread sort / display order

Michael Husbyn wrote:

Is there a way to choose the display order in threaded mode.

Eg:

1 Test
2 Version 2.0 Testing 1
3 Version 2.5 Testing 2
4 Version 2.3 Testing 3

But the preferred sort order (not the ID) is something like this:
1 Test
2 Version 2.0 Testing 1
4 Version 2.3 Testing 3
3 Version 2.5 Testing 2

Example of parameter perhaps:
Thread order = Field1, $id

Or is this something too difficult to implement? Or already there?

Best regards
Michael Husbyn

In summary mode, you can sort by clicking on a column header. You will then see something like

http://.../?sort=Field1

in the address bar. If you now switch to threaded display, this vanishes of course, but you can put a

Start page = ?sort=Field1

into your config file. Use sort for ascending order, rsort for descending order.

1587

Thu Jan 12 15:50:51 2006

Side effects from debugging

Both problems have been fixed in revision 1598.

1586

Thu Jan 12 11:38:13 2006

Side effects from debugging

Addendum: in the Forum, I found a very strange effect: When deliberately highlighting an entry (http://midas.psi.ch/elogs/Forum/?id=1858), the Elog server no longer keeps the page partitioning, but displays ALL entries of the logbook. I don't know if these problems are related, but maybe you could check (we use the "Full" mode for the list view, in case that matters). I have tried to reproduce the problem with our logbook in threaded mode, but we don't seem to have this problem there.

Yoshio

1585

Thu Jan 12 11:32:19 2006

Side effects from debugging

Stefan Ritt wrote:

Thanks for reporting this bug, I fixed it in revision 1597.

Thanks for your quick reaction! Unfortunately, there is one side effect. As far as I understand, you fixed the bug by preserving the command attributes

http://www.logbook.domain/logbook/pageN?command

when browsing with the Goto page links, so that when a filter is applied, it is still active upon page change. However, the same is true for all other commands, including the

?id=NNN

command which is active when clicking List from single entry view. If you click onto, e.g. Previous in this mode, the elogd has a conflict in that it is required to display one page and having to highlight an entry that resides on another.

http://www.logbook.domain/logbook/pageN?id=NNN

The highlighting supersedes, and the page browse links are effectively disabled. Is there a way to keep the bug fix but disable the side effects, e.g. selectively not preserving the

?id=NNN

upon page browsing? Maybe you could implement a "blacklist" of not-to-be-preserved commands, in case there are other problems like this one.

Thanks for the work (I saw the timestamp!)

Yoshio

1584

Wed Jan 11 21:12:13 2006

Re: Getting back from "Find" mode

Yoshio Imai wrote:

Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"?

Yes, just click on the logbook tab on the very top of the page.

1583

Wed Jan 11 21:06:06 2006

Re: Page browsing links in Find mode broken

Thanks for reporting this bug, I fixed it in revision 1597.

1582

Wed Jan 11 15:54:28 2006

Page browsing links in Find mode broken

Hi!

We are having problems with the "Find" mode in the latest revision. When we used "Find" to search for specific texts, and the results span more than one page (say, 2 for example), the page links in the command bar on top point to the ELOG pages rather than the find result pages. This means that, when I click onto "Previous" from find result page 2 (which is the first page getting displayed), I get to logbook page 1 (entries 1 to 20) and not to the previous page of find results. I think this didn't happen in earlier versions. Could you check that? It also happens here in the Forum.

Thanks

Yoshio

1581

Tue Jan 10 19:30:09 2006

Re: Date imports from CSV incorrectly

David Brody wrote:

When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969

Here are the parameters I am using for dates:

Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y

Preset Status Date = $date

Thanks!

DB

Never mind. I figured it out!

Goto page Previous 1, 2, 3 ... 617, 618, 619 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6