ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
676
|
Mon Aug 23 13:43:58 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.5.4 | text display of ascii files not a good idea |
I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea. E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
Then I saw that the ps-file is displayed as text, which is not really
useful.
Probably it is fine to display only files ending in '.txt' per default.
In addition a file that has more than say 1000 lines should probably
also not be displayed (as default, optional OK).
Cheers, Heiko |
675
|
Thu Aug 19 16:20:16 2004 |
| | | | | | |
Here are some things for your wish list:
1) elogd should report quota or disk-full problem: In case a logbook
entry cannot be saved (quota or disk full) then a message like
'Could not save last entry. Please contact administrator.' should
be displayed. Currently nothing happens. Only the submitted
entries 'vanish'.
2) default page view per user, i.e. the 'Back' link goes to
?mode=Full,summary,... depending on the user that is logged in.
Some users complained that 'Back' is not really back. Maybe
consider renaming 'Back' to 'Default View' or something.
3) (related to 1) the 'Back' link should go back to the last used mode
(full, summary, threaded,...) and not to the default mode
4) mark messages as unread/read on a per user basis: The
implementation of this might be quite involved but it would be
rather useful. One way would be to add a default attribute 'Seen
by' to each entry, which lists the login names of the users. Or
files LOGIN_NAME.has_seen can be created which contain the entry
IDs of the viewed entries for each user.
5) alignment of attribute table (using <td colspan=2> for multi line
stuff): see elog:669 :)
You can count my vote for:
- Use "and" and "or" operands in queries
|
674
|
Thu Aug 19 06:21:38 2004 |
| Dave Becker | dbecker@lanl.gov | Question | Linux | 2.5.4 | write access for elogd |
Newly installed elog gives this response when I try to submit a new record:
New entry cannot be written to directory "./logbooks/Linux/"
Please check that it exists and elogd has write access
I started the daemon. I've not yet assigned passwords -- just checking
things out. How can I create this access to my own directory? |
673
|
Wed Aug 18 11:12:56 2004 |
| nait tauh | nait@no2bl.no-ip.com | | Linux | | Admin rights lost after upgrade 2.5.2 to 2.5.4 |
The upgrade was done by just replacing elogd from 2.5.2 to 2.5.4 from the rpm.
Somehow elogd 2.5.4 treat all users as normal user. When clicking on
"config". All admin users has no "change elogd.cfg" button. Revert back to
2.5.2 OK.
Is there anything I need to change to upgrade other than replaceing elogd?
Clearing the cookies didn't help.
Thanks,
.nait. |
672
|
Mon Aug 16 23:49:13 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.4-2 | URL bug in elogd.cfg |
Under 2.5.4-2 build1.460, when I edit the demo elogd.cfg the following happens:
- I start with
URL = http://cde-tx32-sds01.subdom.dom.com:8080/
- When I go to edit the global section of the config file, the *display* of
the string is changed to:
URL = <a
href="http://cde-tx32-sds01.subdom.dom.com:8080/">http://cde-tx32-sds01.subdom.dom.com:8080/</a>
- Saving this results in an error in that the rendered url is invalid.
Our current running version is 2.5.4-build1.413 and this behavior is not
evident. I've looked through the diffs but could not identify the genesis
of this new behavior.
Thanks |
671
|
Mon Aug 16 21:48:49 2004 |
| Steve Jones | steve.jones@freescale.com | Question | Other | 2.5.4 | Re: Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives? |
> > Just for grins, what version of compiler are you using under Linux?
>
> gcc 3.2.2 (from RedHat Linux 9.0)
Well, I am running 2.95.3 - hmmm. We have 3.3.2 - perhaps I'll try that and
see if there is a difference. |
670
|
Thu Aug 12 23:55:00 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.4 | Re: Q: on 'FIND MENU commands =' <menu list> |
> > Thank you. I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
> of logbooks.
>
> You get the "Move To" button only after pressing "Select", otherwise it does
> not make sense. See attached screendump and config example.
Hmmm. I like the little buttons with the pull-downs for selections.
Unfortunately, I don't get that. With a config of:
Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help
my screen only shows the "toggle" and "delete" buttons. Was there a recent rev
that allowed this to happen (I didn't see a comment on this).
BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
to show multiple "Move To" links (one for each logbook) or should there also be
pulldowns?
Thanks |
669
|
Thu Aug 12 23:32:46 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | Linux | 2.5.4 | Re: too many <table> tags |
> > Couldn't one include the extra <table> tag only when there is really more than
> > one attribute per line. All other lines could then be aligned properly.
>
> Sure one can do a lot of things if one has enough time and not tens of other
> requests on the wishlist which really concern some functionality and not just
> cosmetics.
Ouch!
And just to add insult to injury, the same <table> structure doesn't even look the
same between, say, IE6.0 and FireFox 0.9!!
Stefan, keep up the good work! |