Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 269 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Datedown Icon Author Author Email Category OS ELOG Version Subject
  67659   Fri Jan 24 18:59:17 2014 Reply Stephenswgallman@bpa.govBug reportWindows2.9.2Re: Crash report involving propagate and replies

Stefan Ritt wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies.  On the 10th reply the application crashed, this is repeatable 100% of the time.  Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?

/Stefan 

 Unfortunately, I am a little outside of my element when trying to compile it.  I will ask around and see if someone here could give me a hand.  Thanks for looking into this for me.

 

PS.  If anyone else has managed to compile this could you give me a hand =)

  67658   Tue Jan 21 13:17:52 2014 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.9.2Re: [Not] Submit on pressing enter key

Daniel Campora wrote:

Hello community,

I have a feature request for the form of the ELOG.

For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.

Cheers, keep up the good work,

Daniel

Have a look at this forum. If you press <enter> on the subject field, you get asked "do you really want to submit this entry" and you have the chance to cancel and continue editing. You should get the same with the current elog version. 

Attachment 1: Screen_Shot_2014-01-21_at_13.16.48_.png
Screen_Shot_2014-01-21_at_13.16.48_.png
  67657   Mon Jan 20 19:15:24 2014 Question Daniel Camporadcampora@cern.chRequestAll2.9.2[Not] Submit on pressing enter key

Hello community,

I have a feature request for the form of the ELOG.

For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.

Cheers, keep up the good work,

Daniel

  67656   Fri Jan 17 15:59:29 2014 Reply Paolopivato@science.unitn.itQuestionLinux2.9.2-2455Re: Subject attribute in bold type - threaded display

Andreas Luedeke wrote:

Paolo wrote:
Hi all,
I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.
I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.
I've used the following code
Display Subject = <b>$subject</b>
with no success, then I've tried
Subst Subject = <b>$subject</b>
again with no success. It seems that the <b> tag is not iterpreted.
Have you any suggestion about this?
Thank you in advance.
Paolo

 
English (auto-detected) » English
 
T
Hi Paolo,
you've made two little errors, one is partly driven by a bug in the documentation:

1st: If you want to use HTML tags in the display of attributes, you need to add "Allow HTML = 1" in the configuration.

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers
Andreas

 

 

Dear Andreas,

thank you very much for your prompt reply and for you suggestions, which helped me to solve the problem. Now it's all working perfectly.

Cheers,

Paolo

  67655   Fri Jan 17 08:17:09 2014 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2455Re: Subject attribute in bold type - threaded display

Andreas Luedeke wrote:

Paolo wrote:
Hi all,
I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.
I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.
I've used the following code
Display Subject = <b>$subject</b>
with no success, then I've tried
Subst Subject = <b>$subject</b>
again with no success. It seems that the <b> tag is not iterpreted.
Have you any suggestion about this?
Thank you in advance.
Paolo

 
English (auto-detected) » English
 
T
Hi Paolo,
you've made two little errors, one is partly driven by a bug in the documentation:

1st: If you want to use HTML tags in the display of attributes, you need to add "Allow HTML = 1" in the configuration.

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers
Andreas

 

Thanks, I fixed the documentation.

/Stefan 

  67654   Thu Jan 16 19:11:58 2014 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: Subject attribute in bold type - threaded display

Paolo wrote:
Hi all,
I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.
I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.
I've used the following code
Display Subject = <b>$subject</b>
with no success, then I've tried
Subst Subject = <b>$subject</b>
again with no success. It seems that the <b> tag is not iterpreted.
Have you any suggestion about this?
Thank you in advance.
Paolo

 
English (auto-detected) » English
 
T
Hi Paolo,
you've made two little errors, one is partly driven by a bug in the documentation:

1st: If you want to use HTML tags in the display of attributes, you need to add "Allow HTML = 1" in the configuration.

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers
Andreas

 

  67653   Thu Jan 16 11:39:42 2014 Question Paolopivato@science.unitn.itQuestionLinux2.9.2-2455Subject attribute in bold type - threaded display

Hi all,

I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.

I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.

I've used the following code

Display Subject = <b>$subject</b>

with no success, then I've tried

Subst Subject = <b>$subject</b>

again with no success. It seems that the <b> tag is not iterpreted.

Have you any suggestion about this?

Thank you in advance.

Paolo

  67652   Tue Jan 14 21:50:50 2014 Question Grantenzedder@me.comQuestionAll2.9.2Users logged out?

 Hi All,

I'm looking for a way (or if it is even possible?) for users to browse between logbooks without being logged out of their current logbook if they click on a logbook they are not authorised to access?
If they accidentally choose the wrong logbook they are forced to log back in again?

No guest access has been configured on any log.

TIA
 

ELOG V3.1.5-3fb85fa6