On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
"back" submit button.  I can't seem to figure out how to address it.  Suggestions?

> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
> But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
> "back" submit button.  I can't seem to figure out how to address it.  Suggestions?

Can you show us your config? I had this issue when i was initially trying to integrate elog with apache.

 If they have admin rights, the add user button cannot be removed as far as I know.

But even if they can add a user, they only have ability to add a user to the single logbook they are an admin on so they wouldn't be able to add users to other peoples logbooks.

Not sure it helps but that's about all I can really speak to.

Here's the global section and the logbook section for one of the logbooks affected.  Of note, the 'demo' logbook works
fine and does not have this issue.

[global]
port = 8080
SMTP host = localhost
Welcome title = Welcome
Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

[WINTER]

;*****Look and Feel*****
Page title = Winter Weather
List page title =  Winter Weather
Edit page title = Winter Weather
Theme = default
CSS = default.css
Comment = Winter Weather
Title image =

;*****Email*****
Use Email From = me@me.com
Suppress Email to users = 1
Display Email recipients = 0
Email Encoding = 4
Suppress Email on edit = 1

;*****Settings*****
Entries per page = 30
;Reverse sort = 1
Expand default = 2
Display mode = SUMMARY
Mode command = 0
Time format = %d%B%Y-%H:%M
Summary lines = 15
Show top groups = 0
Message height = 8
Message width = 38
Default encoding = 1
Mode commands = 0
Suppress default = 2
Resubmit default = 2
Back to main = 1
RSS Title = $entry time - $Event

;*****MENU*****
List Menu commands = New, Find
Menu commands = List, New, Edit, Find, Reply, Delete

Yes, adding a new attribute in a logbook is not straight forward.

But it is doable: that is one of the things that I write SED scripts for. You just need to add the attribute in all old entries, and in this specific case you can use the entry time to initialise the "when" attribute.

Of course I would only do that on a copy of my data and run a separate elogd server on that data to see if anything is screwed up :-)

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

 

> Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

Your usage of "Top group" is strange. Top groups should only be used for independent groups of logbooks, more like you were running one dedicated sever fore 
a group of logbooks. Further, you defined logbooks (2008, 2009, ...) which do not exist in your config. Why don't you just remove the "Top group" line from your 
config? If you want to group different logbooks, just use the "group" command as written in the docs.

/Stefan

I'm trying to use the command line to post automatically entries from a web based calendar. I run elogd behind SSL with user/pass configuration. I created an account for the calendar and used the following command line.

[gornea@lheppc63 ~]
$ elog -v -s -a Subject=Test -a Type=Notice -a Category=Planning -h svn.lhep.unibe.ch -p 443 -l "LHEP EXO General" -u calendar ******** "SORRY for SPAMMING! Testing automated posts from command line"

It seems like all parameters are OK but for some reason the connection gets closed. Anybody has an idea why? The SSL certificate is not valid and on the web page users have first to accept it. Can this explain the problem? Is there a flag for elog command line to instruct it to ignore SSL warnings? Thanks a lot!

Command line output:

Successfully connected to host svn.lhep.unibe.ch, port 443
Request sent to host:
POST /LHEP+EXO+General/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------16B1637A4CDBB4E6448003F4
Host: lheppc63.lhep.unibe.ch
User-Agent: ELOG
Content-Length: 1105


Content sent to host:
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="cmd"

Submit
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="unm"

calendar
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="upwd"

Z28yQjUyIQ==
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="exp"

LHEP EXO General
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Subject"

Test
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Type"

Notice
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Category"

Planning
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Text"

SORRY for SPAMMING! Testing automated posts from command line
---------------------------16B1637A4CDBB4E6448003F4

Response received:
HTTP/1.1 302 Found
Server: ELOG HTTP 2.9.2-2455
Location: https://svn.lhep.unibe.ch/LHEP+EXO+General/
Connection: Close

<html>redir</html>

Message successfully transmitted, ID=
[gornea@lheppc63 ~]
$
 

I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we link to elog posts that had been discussed during the meeting. We had done this by hyperlinking the URL to the entry. Recently we had to move our logbook to another machine and so none of our hyperlinks work since the URLs have changed. I noticed that when one creates a new entry in the subject they can reference another post. Is there a way to link another elog in the body of the elog by using its logbook name and id number without having to use a URL?

Thanks in advance