Hi all :)

I try to setup my first lobgook, and have some problem. 

I want that Author was preset by $long_name, and it can't change its name. That works correct. I also want, when other user click Reply, that he will be author of reply, but Author windows goes emtpy... No Author, or Reply User in that field. Is it correct?

Do you have any suggestions? 

Here is part of config I use:

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
Preset on reply Author = $long_name

Regards

Daniel.

Hello

I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
Attachments =" is not being read.  Looking at the changelog, I found that
"Number Attachments" has been removed in favor of "enable attachments".  I
tried looking in the documentation but I can't find a discription of the way
 in which multiple attachments are handled.  Can someone give me a pointer?

Thanks
Kevin

Hi

When I upload a message with a attachment (and also without an attachment) I get this message:

"No SMTP host defined in [global] section of configuration file"

However the file and the text have been uploaded. So why does it gives me this message, and how do I work this out?

Best Regards

Tirwit

Hi,

I started re-using after a month an elog on my linux machine and, without any apparent reason since I did not used the machine at all in the last month, every time I try to submit a post I get the following error

"No SMTP host defined in [global] section of configuration file".

The weird thing is that today I created a new logbook using the previous one as a template and, on the new one, I can post without problem (although the configuration is identical).

Do you know what could be causing this?

Thnaks

R

Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"  and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error pops up saying that their username (the admin one, not the new one) already exists. I found the following code:

int save_user_config(LOGBOOK * lbs, char *user, BOOL new_user)
{
   char file_name[256], str[256], *pl, user_enc[256], new_pwd[80], new_pwd2[80], smtp_host[256],
       email_addr[256], mail_from[256], mail_from_name[256], subject[256], mail_text[2000], str2[256],
       admin_user[80], url[256], error[2000], sid[32];
   int i, self_register, code, first_user;
   PMXML_NODE node, subnode, npwd; 

   /* if we outsourced the authentication, use external username */
   getcfg(lbs->name, "Authentication", str, sizeof(str));
   if (stristr(str, "Webserver")) {
      /* do not allow HTML in user name */
      strencode2(user_enc, http_user, sizeof(user_enc));
   } else {
      strencode2(user_enc, user, sizeof(user_enc));
   }
 

which seems to be the culprit:  the admin user is logged using his/her Webserver (http_user) credentials and this overrides anything that he/she might fill in.  If I remove the "Authentication" check then I can create a new user without problems.  So, how to fix this? should the "Authentication=Webserver" check be extended with a self/auto registration check?

[global]
Top group Admin = <...>
Top group Shiftlogs = beamtime1,beamtime2,...

Logbook dir = /data/logbooks

[global Shiftlogs]
Logbook dir = /data/logbooks/shift-logbooks

[beamtime1]
Subdir = beamtime1

I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
development branch (V3.1.0-8196b81):

When I want to "Submit" a new entry, I get a javascript pop-up that asks me:

_This page is asking you to confirm that you want to leave - data you have entered may not be saved._

with the options:
"Stay on page" or "Leave page".

The entry is properly submitted if I agree to "Leave page".
But it is very confusing for my users: they are afraid to loose their entry text.

This problem only shows for some specific logbook configurations.
Below is a minimal logbook configuration that shows this problem:
if you select "entry = short", the pop-up is shown;
if you select "entry = long", the pop-up is not shown, the entry is created immediately.

Attributes = entry, when
Options entry = short{1}, long
Type when = datetime
{1} Show Attributes Edit = entry


(PS: it took me several hours to boil down my 120 line configuration into four lines :-) )