That did the trick, thanks for the fix!

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,

Allen

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.

Hi

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.

Soren

It would be best if I could reproduce your problem. So can you start from a very simple configuration file, add your constraints until the problme happens, and then send me the config file? 

Hi

The problem is not exactly what I thought, but I did track it down. Here is a logbook definition that reliably creates a segmentation fault in e-log. This logbook's only useful purpose is in fact to create a segmentation fault:

You select "New", then "Select", without entering anything.

--------------

Login user = Admin

Attributes = Link

Change Link = <a href="https://$Link"">$Link</a>

---------------

I would be able to create some more debugging information of course, if needed.
 

Regards

Soren

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?

Regards,

Mike

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).