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.

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

 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
 

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

 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]);

                  ^

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 

Yes, the alarm() function is wrong here. I removed it from the Windows version and committed the code to GIT. 

 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.