The automatic hiding behavior is what I'm after, and I've discovered that it is only a problem for PDF attachments. I have reproduced this on the demo logbook on git revision f828049. 

I've taken a look at the source you mentioned, but as far as I can tell, it is just looking for the opening of the img tag in the HTML source, and I'm not sure why that is different for a PDF.

Hi.

Is there any way that "Preset on duplicate" contain ID entry from which it was duplicated?

Cheers

Daniel.

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

Hi,

We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?

Thanks,
Mike

No, I don't think it is possible.

Good Morning,

I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in.  I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes.  However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable.  To expand on this, I may want to even limit the visibility of the attributes as well.

I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this?  Is that section even relevant to what I want to accomplish?

Can anyone provide some guidance?

Thank you for your time & help!

Sincerely,

Terry