ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 429 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 428, 429, 430 ... 806, 807, 808 Next

Thu Jun 4 17:51:50 2009

Memory leak in 2.76 elogd.exe

Hi,

There's seems to be a memory leak with elogd.exe running windows. I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions. I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue.

Thank!

Attachment 1: elogd.jpg

66375

Thu Jun 4 17:51:02 2009

Re: Embedded images break when moving from one book to another.

Stefan Ritt wrote:

Mike wrote:

Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a

particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails

be displayed for each product. This works fine but when we move one message to another logbook the thumbnails

end up getting broken and won't be displayed. The only way to fix this is to remove the image and re-upload the

picture after the message is moved. This is not a good option because we have hundrends of items that are

constantly being moved around from logbook to logbook. Any ideas?

Regards,

Mike

EDIT:

On further inspection it seems that when you are moving messages to another log book the image date filename

is re-written which of course breaks the html link to the image. Is there anyway to supress this so that the filename

stays in tact when it's moved from one book to another. I don't see why the name of an attachment has to get changed

just because something is moved around.

I fixed this in revision #2204. The attachment names now stay the same. There is one tiny risk of screwing up, namely if you have the same attachment name in two different logbooks (accidentally also submitted at the same second and therefore the same time stamp). If you then copy these two entries to a third logbook, one attachment will overwrite the other one, but that risk is indeed really small. I actually had to re-write the link to the attachment inside the text body (even differently for ELCode and HTML encoding). So I'm not 100% sure I covered all cases, so just give it a try.

This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?

Thanks Stefan!

Mike

66374

Thu Jun 4 15:37:44 2009

Re: Embedded images break when moving from one book to another.

Mike wrote:

Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a

particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails

be displayed for each product. This works fine but when we move one message to another logbook the thumbnails

end up getting broken and won't be displayed. The only way to fix this is to remove the image and re-upload the

picture after the message is moved. This is not a good option because we have hundrends of items that are

constantly being moved around from logbook to logbook. Any ideas?

Regards,

Mike

EDIT:

On further inspection it seems that when you are moving messages to another log book the image date filename

is re-written which of course breaks the html link to the image. Is there anyway to supress this so that the filename

stays in tact when it's moved from one book to another. I don't see why the name of an attachment has to get changed

just because something is moved around.

66373

Thu Jun 4 15:21:23 2009

David Pilgram

David.Pilgram@epost.org.uk

Question

Linux

2.7.6-2191

Re: Moving entry (and replies) from one log book to another

Hi Stefan,

Any possibility on this one?

David Pilgram.
> Hi Stefan,
> 
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$).  While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
> 
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
> 
> Thanks,
> 
> David Pilgram.

66372

Thu Jun 4 14:44:11 2009

Re: help with substituting subjects

Alexander Withers wrote:

I am trying to add additional information to the subject of new entries:

Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject

However, the new entry subject looks like:

this is my subject [INCIDENT this is my subject [INCIDENT $message id]

I'm not sure if there's a problem with the substitution or if this is just not allowed (I'm having LISP flashbacks).

By the way, if I use "Subst on reply subject" I get the behavior I would like but the original entry in the thread doesn't contain the appended data:

Subst on reply subject = Re: $subject [INCIDENT $message id]

Any help would be appreciated.

Alex

The problem here is that the subsitution is executed before the entry is committed to the database. The message ID is assigned however only in the commit. So at the time of the substitution, the $message id is not available. When you do the reply however, the message id is valid and subsituted correctly. I see at this moment no clever solution for your problem (maybe "Subst on edit", but then you have to edit/submit each message manually once).

66371

Thu Jun 4 14:37:54 2009

Re: User can modify Fixed Attributes Edit when selecting preview

Allen wrote:

Hi. I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.

I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields. When I click the edit button, everything looks restricted as it should be, but if I click Preview, the user is then able to change the fixed attributes.

Is there anyway to remove the preview button inside the edit page, or is anyone else having this issue?

Thanks for reporting this bug. I fixed it in revision #2203.

66370

Thu Jun 4 14:05:58 2009

soren poulsen wrote:

I am having a little problem with e-log that I can easily reproduce.

I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.

So this only happens when I am not observing the input formats or the mandatory fields.

This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.

Server listening on port 8079 ...

Program received signal SIGSEGV, Segmentation fault.

0x0000000000414077 in is_script (

s=0x7fff1a0b89a0 "<a href=\"https://edh.cern.ch/Document/DAI/\"\"></a>")

at src/elogd.c:5414

5414 for (i = 0; script_tags[i][0]; i++) {

(gdb)

Soren

I had finally the same problem. This is due to a bug indeed inside is_script(). It has been fixed in revision 2201.

66369

Thu Jun 4 14:04:21 2009

Re: Supress Email to Author of a message?

Mike wrote:

I couldn't find an obvious solution to the problem. I'd like to suppress email

notification to the author of a message. I've had some people complaining

that when they use elog they don't want to get an email about what they wrote

since they wrote it.

Is it possible?

Actually I do want to receive a copy, just to be sure that the emails got sent out correctly. I agree that an option would be good for that but it's not implemented right now. An alternative solution is to define a filter in their email client to discard these messages (like if subject contains ELOG and sender equals your own mail address).

Goto page Previous 1, 2, 3 ... 428, 429, 430 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6