| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2165
|
Wed Mar 14 11:55:54 2007 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Question | Linux | Windows | 6.4-1802 | sort attributs |
hello,
For 1 event, I need the date and the hour of this one. An event can be enter in elog several days after this one. The problem is that I do not manage to carry out one sorts on these two attibuts. I tested the order “? rsort” but this one works only on one entry not out of 2 at the same time (? rsort=Heure+evenement, Date+evenement&mode=threaded)
have an easy way?
Thank you very much
Xavier Deletoille |
| Attachment 1: elog14_03.jpg
|
|
|
2164
|
Wed Mar 14 11:31:35 2007 |
| deletoille | xavier.deletoille@synchrotron-soleil.fr | Question | Linux | Windows | 6.4-1802 | submit modified elog entry |
hello, I have small a bug,
when I create an entry. Per moment the program requires of me: "Submit modified Elog entry"
if I answer yes, Eog create 2 entry identical.
If I answer not it create only one.
I don't wait that elog asks me a confirmation
Any Ideas,
Thanks in advance |
|
2163
|
Tue Mar 13 20:58:07 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Justin Ellison wrote: | It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
|
Conditional attributes? Like:
Attributes = ..., Status
Options Status = Open{1}, Closed{2}
{2}Locked attributes = Status
Unfortunately once it's locked, the admin has to change the config file to unlock it. |
|
2162
|
Tue Mar 13 17:27:49 2007 |
 | Justin Ellison | justin@techadvise.com | Request | | Current | Addition of a "Restrict edit attribute" option? |
It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
Sound plausible?
Justin |
|
2161
|
Mon Mar 12 20:35:17 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? |
| Justin Ellison wrote: | The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
In revision 1809 I implemented the options
Show attributes = ...
Show attributed edit = ...
The first one is for the log entry page, the second for the entry form. This way you can distinguish between the bug number and the link. The old option Hidden attributes has been dropped, since it has the same effect now as Show attributes edit. |
|
2160
|
Fri Mar 9 22:14:57 2007 |
| Justin Ellison | justin@techadvise.com | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? |
| Any takers? |
|
2159
|
Thu Mar 8 08:08:42 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.4.1801 | Re: Search all logbooks as default |
| An Thai wrote: | | do you know how I can default set the option "Search all logbooks" in the Find page selected/checked? |
I added the option
Search all logbooks = 2
which lets you do that. It's in the SVN version and will be contained in the next release. |
|
2158
|
Tue Mar 6 17:03:43 2007 |
 | T. Ribbrock | emgaron@gmx.net | Bug report | Linux | 2.6.4 | Re: Upgrade to 2.6.4 broke quick search |
| T. Ribbrock wrote: |
[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back [...]
|
Apparently, this must have been some session-oddity - I just logged out and got an error message about a bad URL. I then went to the base URL of the logbook (i.e. http://server:8080), chose the correct logbook and logged in again. Things work fine since. No idea what went wrong the first time round... 
Regards,
Thomas |