Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 330 of 808  Not logged in ELOG logo
icon5.gif   some menu commands formed with broken links, posted by Ken Ludington on Tue May 7 22:15:37 2013 
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?
    icon2.gif   Re: some menu commands formed with broken links, posted by Garret Delaronde on Fri May 10 17:24:55 2013 
> 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.
    icon2.gif   Re: some menu commands formed with broken links, posted by Ken Ludington on Fri May 10 19:26:50 2013 
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
    icon2.gif   Re: some menu commands formed with broken links, posted by Stefan Ritt on Fri May 17 15:26:50 2013 
> 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
icon1.gif   Daemonizing vs. shell execution, posted by Martin Rongen on Mon Jun 3 15:44:46 2013 

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

    icon2.gif   Re: Daemonizing vs. shell execution, posted by Stefan Ritt on Mon Jun 3 15:53:22 2013 

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

    icon2.gif   Re: Daemonizing vs. shell execution, posted by Martin Rongen on Tue Jun 4 13:26:02 2013 

Stefan Ritt wrote:

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

 I didn't know that. Thanks for the quick response. I have it working now :)

icon1.gif   Enforce new thumbnails, posted by Martin Rongen on Mon Jun 24 15:46:43 2013 

Hi everyone

The past few days I have been editing elogd.c to link all image files to the PIXLR-API (http://pixlr.com/). I am now at a point where the edited images are uploaded fine to the elog server, but in order for the thumbnails  to refresh one needs to click edit and thus load the FCKeditor for the corresponding entry.

Any suggestions how I may be able to enforce thumbnail generation, whenever the entry is displayed.

An alternative way might be to get the original entry id associated to an attachment, but I have not been able to achieve this either.

Best regards

Martin

ELOG V3.1.5-3fb85fa6