hyperlink other elog posts, posted by Remington Tyler Thornton on Tue May 28 19:01:42 2013
|
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 |
Re: hyperlink other elog posts, posted by Andreas Luedeke on Wed May 29 14:57:23 2013 
|
Remington Tyler Thornton wrote:
I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we |
|
Elog command line problem, posted by Razvan Gornea on Tue May 28 09:16:18 2013
|
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 ~] |
|
Admin delete option, posted by Hal Proctor on Wed May 22 22:24:14 2013
|
How can I show the Delete option for Admins?
So I have a logbook with the following config:
|
|
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
|
|
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
|
|
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.
|
|
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 |
|
Kerberos on Windows server, posted by Hal Proctor on Mon May 13 16:44:05 2013
|
| Does anyone have a success story with kerberos on windows? |
|
Re: Kerberos on Windows server, posted by Hal Proctor on Thu May 16 16:29:16 2013
|
Hal Proctor wrote:
|
|
Multi Language based on logged on user?, posted by Hal Proctor on Thu May 16 15:41:34 2013
|
| Can ELog support different languages based on the logged on user? |
|
Auto-Generate new logbook daily, posted by Ryan Blakeslee on Fri Apr 26 22:29:50 2013
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers
work history 2. having a searchable knowledge base for future reference. |
|
Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 11:53:41 2013
|
Ryan Blakeslee wrote:
Hello, |
|
Re: Auto-Generate new logbook daily, posted by David Pilgram on Sat Apr 27 13:21:38 2013
|
Stefan Ritt wrote:
|
|
Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 15:30:28 2013
|
David Pilgram wrote:
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes |
|
Re: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon Apr 29 10:17:54 2013
|
David Pilgram wrote:
|
|
Re: Auto-Generate new logbook daily, posted by Ryan Blakeslee on Tue May 7 04:57:37 2013
|
Andreas Luedeke wrote:
|
|
Re: Auto-Generate new logbook daily, posted by David Pilgram on Tue May 7 11:54:23 2013
|
Ryan Blakeslee wrote:
|
|
Re: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon May 13 22:31:37 2013
|
David Pilgram wrote:
|
|
admin user access admin page, not config page, posted by Szu-Ching Peckner on Tue Sep 18 17:57:47 2012
|
We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user. |
|
Re: admin user access admin page, not config page, posted by Garret Delaronde on Fri May 10 17:37:24 2013
|
Szu-Ching Peckner wrote:
We have multiple logbooks. Each user is admin user for his/her own logbook. |