Using select menu option to move multiple logbook entries to another logbook, posted by Robin Peterson on Fri Jun 4 22:40:44 2004
|
I'm trying to configure this thing to be able to filter on a set of
criteria, choose select, choose toggle all, and then choose "Move to
Complete Work Requests".
I've been able to select a specific logbook entry and move it, and I've
been able to filter and select and toggle, but I can't figure out how to
get the Move To option to show up on the main logbook menu....
what am I missing?
robin |
Re: Using select menu option to move multiple logbook entries to another logbook, posted by Stefan Ritt on Mon Jun 7 15:58:10 2004 
|
> I've been able to select a specific logbook entry and move it, and I've
> been able to filter and select and toggle, but I can't figure out how to
> get the Move To option to show up on the main logbook menu....
To be able to move entries between logbooks, you have to enable the "move to"
command with the option "Menu commands" like:
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Move to, Help
Having done this, the menu "Move to xxx" should show up when you select an
individual entry, where xxx is the name of the other logbook(s). If you so a
"Select" on several entries, a new button should show up which lets you move
all selected entries to the other logbook(s). See elog:/1 for an example. If
you do not observer this behaviour, please let me know. |
'Full' mode gives incorrect results when searching, posted by Bartjan Wattel on Wed Jul 14 11:45:46 2004
|
Hi,
I was just searching your online discussion forum for entries with the
word 'password' in the subject. I noticed that the 'Full' option in
the 'full/summary/threaded' line displays the results of all entries in the
logbook, and not only the entries with the word 'password' in the subject.
I think there is an error in the URL, because when looking for the word
password in the subject, the URL for the 'Full' option is:
http://midas.psi.ch/elogs/Forum/page1?mode=full&reve&npp=8&Subject=password
If I change the word 'reve' in this URL to 'reversed=1', the results are
correct
Bartjan Wattel |
|
Re: 'Full' mode gives incorrect results when searching, posted by Stefan Ritt on Wed Jul 14 12:12:35 2004
|
Thanks for pointing out this bug. I fixed it. New version under CVS. |
|
?cmd=New&pType=PC does not work, posted by Guenter Nowak on Fri Jul 30 02:03:59 2004
|
according to the users guide,
http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
should create an entry with the type value set to PC, but this doesn't work |
|
Re: ?cmd=New&pType=PC does not work, posted by Stefan Ritt on Fri Jul 30 09:15:39 2004
|
> according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Now it works. Updated elog version under CVS and as a snapshot (see Download Page) |
Re: ?cmd=New&pType=PC does not work, posted by Guenter Nowak on Fri Jul 30 12:26:10 2004
|
> according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Thanks! |
, posted by on 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
|