Hi,

I'm trying to increase the entry text constraint but not sure how to do this.  Couldn't find it in the documentation or may be I missed it.  Appreciate your help.

Thanks.
Illam

Hi Illam

You actually have to change the source code of elog and then recompile. Download the code from https://bitbucket.org/ritt/elog/src/master/, change the value of the variable TEXT_SIZE in the file src/elogd.h

Default ist #define TEXT_SIZE 250000

Hi,

I am trying to implement a Custom input forms by following this  https://elog.psi.ch/elogs/Contributions/49. Is there a way to also insert an image or files to it? I want to take a snap from the iPad and want that to go as an attachment or attach a file(s) into the form. Is there a way to do that?

Your suggestions are highly appreciated.

Regards,

sjena

When you submit a "normal" elog entry, you can click on "Choose file" to add an attachment. On a mobile device, you will then be asked to select a photo from your library or take one with your camera. You can do the same on a custom form. You have to extract the code from the normal submissoin form and program it on your custom page. It needs however some work and might not be straight forward.

Stefan

Thanks Stefan,

I am not yet able to figure out how attachment submission is done, I am trying. It would be helpful if you can refer me to some pointer.

With regards,

satyajit

The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions.  I don't see any update/change to that rule anywhere in the docs.

I have been using multi-character condition names successfully.   I find these are easier to use since they can be more descriptive of each condition.   It works, but I am concerned I may be doing something that might not be supported going forward.   (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)

Thank you, again, for this fine (and, may I add, fun?) tool.  I'm having a good time with it!

You can easily use multi-character conditionals, up to 256 chars.

Could we update the doc for this?

According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

Same problem here, in version 3.1.3.   It would be very nice if this worked.

For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...

Allow HTML = 1

Periodically (rarely) on manually adding a record into Elog it generates a duplicate record with its own incremented ID and I don't know why. I just delete the duplicate in the meantime but would like to know if anyone else has seen this and whether their is a answer/fix for it. Thanks.

I've seen exact;y this effect, even though I have branching = 0 in my config file - so ordinarily no chance to have two
 replies to an entry.  My pointer aka mouse (I'm on Linux) is a bit dodgy, and sometimes disconnects/reconnects, so in effect gives a very fast double click.  I've always assumed that was the cause of the problem.  The two replies have incremental IDs, and both those IDs are listed in the "Reply to" header section of the entry.  I'm not sure how this overcomes the branching = 0 detail, though.

That is what I have assumed, but if others see this on occasion, perhaps it's got a different cause.

I find that I can reply to a message ("original" message, if you will) without doing anything to the reply message (the "copy" of the original message, if you will).  If I then submit it, it gets saved as a new message, identical to the one I replied to.

I read through the options at the end of the docs.  I did not see anything about a way to suppress identical messages, or a way to force the user to make some kind of change to make the reply different from the original.

I'm not sure if this is what you want.

If you want to prevent "accidental" replies being identical to the original message, you can force a situation where the user will be alerted that they have to do something if they really want to make a reply. 

An example.  I have an attribute "Action".  In order to make a reply.  I have set up that I must select an Action attribute every time.  If I forget, I get an error message screen, and can click to go back to the entry and have another attempt (nothing is deleted if you have added to the reply).

In the elog.cfg file, I have the lines

Required Attributes =  Action

Preset on reply Action = 

This hopefully would remind them that they are making a reply to an entry, and either make a reply, or abort the attempt.

I was only commenting on the predicament as I have run into it also.  I have required fields, but short of some sort of "abort" control (curiously missing from the otherwise vast offerings of elog), I don't see any way to ensure that identical replies don't occur in any circumstance that may arise.

My feeling is that an additional option to elog is appropriate, one that disables -- completely -- identical replies to a message.   I am not asserting that this must be done, just that it might be the only truly efficacious way to eliminate this issue.   Again, I was only commenting on it, but I would like to see such a feature implemented in elog.  I believe it can be justified because this would seem, intutitively, to be a potential problem for almost anyone using elog. 

I hope you will receive my response here in the constructive and friendly manner it is intended.

Hi Harry,

I'm just an elog (ab)user, not one of the developers.  My original 2017 reply was to report an issue that was due to hardware, but somehow overcame a configuration flag (no multiple replies to a single entry), which might have been the same problem as the original poster, Alan Grant, was observing, where one real reply mysteriously became two identical ones.  That appears to be different to the issue you have.

There is an "Abort" button; in version 2.9.2 it is "Back" (without a warning), somewhere along the development it because "Delete" (with a warning), but that only covers circumstances where a reply is started by accident/unintentionally and then it is realised.  My previous suggestion certainly would alert the replier that they have to do something - even if only selectiing an "Action" - before the new entry would be accepted,  This suggests that you have a circumstance where the reply being a duplicate of the entry is a real issue, and that neither of the suggestions above would help.  Don't forget, some people may *want* this.

It would be for Stefan and Andreas to put this on the elog wish-list.  I am a little puzzled as to how your problem arises - lazy user? - so perhaps more comment as to how this is occurring will help Stefan and Andreas understand the why.  There is somewhere on this site a page where you can add suggestions for the wish-list, but due to security certificate issues, I can only access the Forum at present and cannot point you to it.

Hey all,

In the configuration of the Elog one can use

Preset Author = $long_name
Preset Author Email = $user_email

to have predefined values for the Author and Author Email fields when creating a new entry via the web interface.
Is it also possible to use these placeholders when creating a new entry via the Python API?

Cheers,
Florian

Query

(FYI, OS = FreeBSD, Elog Version as showing on logon box = V3.1.4-)

Is it possible to use both Style <attribute> and Cell Style <attribute> on the same row?
For example, have a Logbook containing several Attributes and display a subset of those attributes in Summary Mode. Two attributes are of interest for this query which are part of the attributes displayed in Summary Mode, attributes ‘Assign Line’ and ‘Service’ 

If the ‘Attribute Assign Line = Assign 1’ then shade all cells in that row #808080
but if the ‘Attribute Service = 1600’ always shade that cell #7A5776 

Config file includes
Style Assign Line Assign 1 = background-color:#808080
Cell Style Service 1600 = background-color:#7A5776

The result is the row gets shaded #808080 if ‘Assign Line = Assign Line 1’ but fails to shade the Service cell colour #7A5776 if it equals 1600 

Extract from HTML source for the ‘1600’ cell when both conditions are correct shows both background-color values are present and the cell is styled the first value listed (which is Style Assign Line Assign 1 = background-color:#808080 but I always want #7A5776 for cell Service when it is of value 1600)
.
<td class="list2" style="background-color:#808080" style="background-color:#7A5776"><a href="../Daily/1">1600</a></td>  

Thank you,

David