ELOG Forum

As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now.

A quick (relative term, that) search usually finds the entry which references the missing "Reply to" line, and editing that, all is well. I'm not sure how this can happen, but it does. NB, I'm still on elog 2.9.2 so I don't know how the draft facility works and possibly enhances the possibility of this issue.

Note that this is different to the case (rather more frequent) where the entry in the "In reply to" field is missing. This causes elog to go into a continuous loop and only the strongest measures ("kill -9 xxxx in linux) will break this out. This can happen more frequently as if you delete a thread with a large number (>40?) of entries, elog crashes, but more importantly, hasn't finished the job. Clicking on the remenents of the thread (which are usually the later entries) causes the endless loop.

Andreas Luedeke wrote:

It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".

I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.

For new entries one would need to make the logging print line later - but that would blow up the code.

The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.

Andreas

Sergio Navarrete wrote:

I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes

Date Time [User@IP] {Logbook} NEW entry #0

How can I make the #0 be the real entry number for the reply?

68856

Sat Oct 27 10:51:12 2018

Re: messy code for chinese charactor

Can you post a screenshot?

Wenhao Huang wrote:

The Chinese character appears messy code. The encoding way is the default utf-8. How can I solve this problem?

68855

Fri Oct 26 19:15:19 2018

Devrim Esenturk

devrim.esenturk@gmail.com

Bug report

Linux

V3.1.3-7933898

Re: How many "Extendable options" can I add?

No problem :)

Your suggestion worked as it must be. I didn't see "Extendable options = <list>" on guide :/

I guess I need rest a little bit... :(

Thank you

Have a great weekend

Devrim

Grant Jeffcote wrote:

Apologies that should have been Devrim (autocorrect again) :-(

Grant Jeffcote wrote:

David,

Try

Extendable options = Require Model, Require Lens, Require Other,

Regards

Grant

Devrim Esenturk wrote:

I am trying to add "Extendable options" for some attribute as below example. However button to add new item for list appears only for the first "Extendable options", if disable the first with (;), button appears for the second. It means elog add new item button only the first line "Extendable options" not for other?

Is this a limitation or bug or am I doing something wrong?

Options Require = N/A, Camera{1}, Lens{2}, Other{3}
{1} MOptions Require Model= XNB-6001, PNM-7000VD, PNM-9000VQ, PNM-9320VQ
{2} MOptions Require Lens = SLA-T2480, SLA-T2480V, SLA-T4680, SLA-T4680V, SLA-T1080F, SLA-2M2400P, SLA-2M2800P, SLA-2M3600P, SLA-2M6000P, SLA-2M1200P, SLA-5M3700P, SLA-5M4600P, SLA-5M7000P, SLA-2M2400Q, SLA-2M2800Q, SLA-2M3600Q, SLA-2M6000Q, SLA-5M3700Q, SLA-5M4600Q, SLA-5M7000Q, SLA-2M2400D, SLA-2M2800D, SLA-2M3600D, SLA-2M6000D
{3} MOptions Require Other = Base Unit

Extendable options = Require Model

Extendable options = Require Lens

Extendable options = Require Other

Thank you

Devrim

68854

Fri Oct 26 16:50:48 2018