ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66472
|
Tue Jul 28 16:30:46 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Odd problem (bug?) with certain attribute | I have the following simple test logbook:
; General
List display = Edit, Hostname, OS, Size
Entries per page = 150
Quick filter = OS
Date Format = %d/%m/%Y
Summary Lines = 0
; Attributes
Attributes = Hostname, OS, CPU,Size
Required Attributes = Hostname
Sort Attributes = Hostname
; Message part: log is text only, but elog is allowed
Default encoding = 0
Allowed encoding = 2
For some strange reasons, I'm having problems with the "Size" attribute, which I have added later. If I start adding/editing entries, at some point, the "Size" attribute will stay at "0" and will not accept any further changes. I've tried to pare down the config to maybe find which statement could be causing this, but to no avail. The only thing I can say is taht id doesn not seem to happen if the configuration consist of the sole line
Attributes = Hostname, OS, CPU,Size
I'm quite puzzled as to what is going on here (the original problems stems from a more complicated logbook) - I'm not even 100% sure whether this happens due to a bug or not.
Regards,
Thomas |
66500
|
Thu Aug 6 22:29:12 2009 |
| Erik Iverson | eiverson@ornl.gov | Question | All | 2.7.3 | Pre-populate Attachments in URL | Is there a way to pre-populate the new entry window with one or more attachments? Per the documentation, this is easy to do with attributes, i.e., http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Info as a URL or bookmark will do it. I'd like to do the same thing with attachments, for example http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Photograph&attfile1=picture1.jpg&attfile2=picture2.jpg might prepopulate two attachments, giving me an edit window all ready to enter the brief description represented by the two pictures. |
66519
|
Mon Aug 24 21:47:14 2009 |
| Allen | bastss@rit.edu | Bug report | Linux | 2.7.7-2246 | Fix text prevents user from editing text during creation, instead of just edit | When we set Fix text = 1, according to the syntax, this should prevent users from modifying the text field during an edit, but it looks like it is blocking access at both time of edit and creation, meaning you can never add anything to it. Is that the intended functionality? |
66520
|
Tue Aug 25 21:08:51 2009 |
| Arno Teunisse | A.teeling3@chello.nl | Question | Windows | 2.7.7-2246 | fckeditor update | Hello
Just a few fckeditor related questions. How do elog versions and fckeditor versions relate. ?
Can I just drop another version of the fckeditor over an other version? What things should I consider when doing so ?
thanks for you're time.
|
66522
|
Tue Sep 1 04:15:57 2009 |
| james Goedsir | james.goedsir@stratosglobal.com | Question | Windows | 2.7.7 | Time Display Format | My Time field is displayed i a 12 Hour format I would like to change it to 24 Hours, can someone advised how it can be done |
66585
|
Mon Nov 9 11:50:05 2009 |
| Eddy Berends | eddy.berends@stratosglobal.com | Bug report | Linux | 2.7.7 | Reply on item not allowed moving item to other logbook | After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
66638
|
Thu Dec 3 20:25:50 2009 |
| Allen | bastss@rit.edu | Bug fix | Linux | 2.7.7 | elogd keeps crashing, any thoughts? | We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see:
Dec 3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
Any thoughts? |
66659
|
Sat Jan 2 01:34:57 2010 |
| Gabriele Sirri | sirri@bo.infn.it | Request | Windows | 2.7.8-2280 | Collapse to Last and Quick Filter | Hello,
I feel that the filter result could be confusing and unexpected when "COLLAPSE TO LAST" is enabled: you
filter the first entry but you show the last one. What is filtered doesn't correspond with what is shown (look
the attached example).
I suggest to implement an option to let the user decide which entry (first or last) should be retrieved for
filtering (a tentative patch is attached).
Thank you
Gabriele
P.S. A similar behaviour occurs when you sort the logbook: it could appear as not sorted because you sort the
first entry but the last one is shown. |
Attachment 1: example.txt
|
Example:
Consider the Status attribute to define the progress of a task:
Attributes = Author, Task, Status
Options Status = Start, Step1, Step2, End
Thread Display = Task, Status
and logbook with three thread arranged like this:
|-- Task0, Start
| |-- Task0, Step1
| |-- Task0, Step2
|
|-- Task1, Start
| |-- Task1, Step1
|
|-- Task2, Start
It is collapsed to:
+-- Task0, Step2
+-- Task1, Step1
|-- Task2, Start
Now, if you filter the Status using the "Start" value, you obtain again:
+-- Task0, Step2
+-- Task1, Step1
|-- Task2, Start
In my opinion, this is a bit confusing.
Using Step1 or Step2 values, nothing is selected (also confusing).
|
Attachment 2: elogd.c.patch
|
Index: elogd.c
===================================================================
--- elogd.c (revisione 2280)
+++ elogd.c (copia locale)
@@ -19539,6 +19539,19 @@
if (status != EL_SUCCESS)
break;
+ if ( getcfg(lbs->name, "Filter last entry", str, sizeof(str)) && atoi(str) == 1 ) {
+ /* search last entry in this thread */
+ if (reply_to[0]) {
+ search_last_reply(msg_list[index].lbs, &message_id);
+ size = TEXT_SIZE;
+ status =
+ el_retrieve(msg_list[index].lbs, message_id, date, attr_list, attrib, lbs->n_attr, text,
+ &size, in_reply_to, reply_to, attachment, encoding, locked_by);
+ if (status != EL_SUCCESS)
+ break;
+ }
+ }
+
/* apply filter for attributes */
for (i = 0; i < lbs->n_attr; i++) {
|
|