Re: Thread view problem in searches, posted by soren poulsen on Tue Mar 16 11:58:55 2010
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
That sounds fine but I think there is a problem with rendering under Opera. I enclose a screen shot: There is too much white space in the lines, it seems  $
The problem only appears in Find
|
I just tried myself with V10.50, and things work fine, even in the find page:
Can you try on the forum, just to check if it's specific to your configuration?
|
Thanks. The Forum is fine. The problem is - apparently - specific to my installation. The white space origins in long sequences of " " (repeated); in the lines in Find.
Let me re-install with the latest version and see if I can solve it like that.
Soren
|
I have re-installed the latest, fastest, smartest, brightest version. And it all works perfectly! Thanks a lot for your help.
Soren
|
Everything is fine. But my users do not like that the threads are broken into individual entries and not shown as full threads as before. So I am stuck with the "old" version. This is probably asking for too much but would it be difficult to have a flag to specify if you want to benefit from the new behaviour or keep pre-2282 behaviour (with its inconvenience which led to the presentation change). It could even be a compile tag flag, if it just me (well, my users) who is asking for this.
Soren |
Re: Thread sort / display order, posted by Stefan Ritt on Thu Jan 12 16:06:16 2006
|
| 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. |
|
Re: Themes BUG ?, posted by Stefan Ritt on Mon Feb 24 13:22:06 2003
|
> Is the DEFAULT theme somehow hardcoded for the login screen and the main
> menu ?
Yes, this was in and certainly is not correct. So I fixed it, the new code
can be obtained vom CVS (see elog:233). |
|
Re: The Chinese Language,Demo Configuration and Help Files, posted by Stefan Ritt on Mon Oct 10 12:53:46 2005
|
| Exaos Lee wrote: | | I want to make elogd display the date in Chinese format. Please tell me howto. |
Thank you for the files.
If you specify
Language = zh_CN
Then elogd looks for a file "eloglang.zh_CN" for the translation, for a file "eloghelp_zh.html"
for the help, and does a
setlocale("zh_CN");
to switch to Chinese date format. To retrieve the date, elogd calls strftime("%x"); |
|
Re: Text column in the main list, posted by Stefan Ritt on Fri Oct 20 13:28:38 2006
|
| Alexandre Lindote wrote: | Is there a way of removing the "Text" column from the main listing of a logbook?
I have a logbook that works as a document database, and I don't even allow the entering of text... But the column insists on appearing! 
|
Summary lines = 0 |
|
Re: Text column in the main list, posted by Alexandre Lindote on Fri Oct 20 13:36:29 2006
|
| Stefan Ritt wrote: |
| Alexandre Lindote wrote: | Is there a way of removing the "Text" column from the main listing of a logbook?
I have a logbook that works as a document database, and I don't even allow the entering of text... But the column insists on appearing!
|
Summary lines = 0 |
Great! Thanks a lot
Alex |
|
Re: Text Limit for Subject line, posted by Stefan Ritt on Thu Feb 26 10:01:37 2009
|
| Robert Risher wrote: |
|
Is there any way I can limit the ammount of characters in the Subject line?
Thank you,
|
Use the
Format Subject = ...
option as described in the manual. The last parameter is the "maximum number of characters allowed". |
|
Re: THREAD DISPLAY = sucks up coded spaces, posted by Stefan Ritt on Sun Aug 8 16:25:09 2004
|
> I was trying to do some hard coded spaces using:
>
> Thread display = For: $Date for Shutdown. $DataCenter:
> $short summary. Coordinator: $Shutdown Coordinator.
>
> The spacing actually works mthe first time, but upon going back into editing
> the config file, the coded spaces are gone, replaced with real spaces, and
> when saved all real multiple spaces are, as one would expect, ignored. The
> spacing reverts back to normal.
>
> I tried other html tags but these show up as literals.
I fixed that in revision 1.448. The problem also showed up even in normal
logbook entry displays and in replies (before this fix, the in this text
whould not have shown up). Get the new version from CVS. |