ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67655
|
Fri Jan 17 08:17:09 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2-2455 | Re: 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 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2-2455 | Re: 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 |
| Paolo | pivato@science.unitn.it | Question | Linux | 2.9.2-2455 | Subject 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 |
| Grant | enzedder@me.com | Question | All | 2.9.2 | Users 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
|
67651
|
Tue Jan 14 08:15:19 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
Ed McNichol wrote: |
Stefan Ritt wrote: |
A.G. Schubert wrote: |
Stefan Ritt wrote: |
A.G. Schubert wrote: |
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!
|
SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon.
|
I too am having issues installing on Mac OS X 10.9.1. I changed CFLAGS in makefile to;
CFLAGS += -O3 -funroll-loops -fomit-frame-pointer -W -Wall -D_FORTIFY_SOURCE=0
I get many lines of errors like this when I run make;
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/openssl/ssl.h:1491:6: note: 'SSL_accept' declared here
int SSL_accept(SSL *ssl) DEPRECATED_IN_MAC_OS_X_VERSION_10_7_AND_LATER;
^
src/elogd.c:28809:19: warning: 'SSL_set_fd' is deprecated: first deprecated in OS X 10.7 [-Wdeprecated-declarations]
SSL_set_fd(ka_ssl_con[i_min], ka_sock[i_min]);
^
|
If you would use the Makefile from the GIT repository there would be no errors under OS X 10.9.1:
/elog$ make
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -w -c -o crypt.o src/crypt.c
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -o elog src/elog.c crypt.o -lssl
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -w -c -o regex.o src/regex.c
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -w -c -o auth.o src/auth.c
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -c -o mxml.o ../mxml/mxml.c
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -c -o strlcpy.o ../mxml/strlcpy.c
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -o elogd src/elogd.c crypt.o auth.o regex.o mxml.o strlcpy.o -lssl
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml -DHAVE_SSL -o elconv src/elconv.c -lssl
/elog$
Actually what you need is -Wno-deprecated-declarations to suppress the warnings. The open SSL functions will at some point be removed from OSX, they have their own implementation of SSL. So then we either have to ship openSSL together with elog or use Apple's implementatoin. But for now we are still fine.
/Stefan
|
67650
|
Tue Jan 14 05:19:47 2014 |
| Ed McNichol | ed@mcnichol.com | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
Stefan Ritt wrote: |
A.G. Schubert wrote: |
Stefan Ritt wrote: |
A.G. Schubert wrote: |
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!
|
SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon.
|
I too am having issues installing on Mac OS X 10.9.1. I changed CFLAGS in makefile to;
CFLAGS += -O3 -funroll-loops -fomit-frame-pointer -W -Wall -D_FORTIFY_SOURCE=0
I get many lines of errors like this when I run make;
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/openssl/ssl.h:1491:6: note: 'SSL_accept' declared here
int SSL_accept(SSL *ssl) DEPRECATED_IN_MAC_OS_X_VERSION_10_7_AND_LATER;
^
src/elogd.c:28809:19: warning: 'SSL_set_fd' is deprecated: first deprecated in OS X 10.7 [-Wdeprecated-declarations]
SSL_set_fd(ka_ssl_con[i_min], ka_sock[i_min]);
^
|
67649
|
Mon Jan 13 09:30:09 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
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 |
67648
|
Mon Jan 13 09:01:31 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
I don't see it has crashed when testing your cfg. However, one thing I must do is to comment out the alarm_handler function in order to compile the elogd successfully. Otherwise, it shows an undefined alarm, see in the 2nd attachment. Although it did not crash as tested with your cfg, I have experienced the new version sometimes crashed on our system but then it self restarted (different scenario since my cfg does not use Propagate. I have not been able to narrow down yet.
|
Yes, the alarm() function is wrong here. I removed it from the Windows version and committed the code to GIT. |
|