Re: Blockying user access, posted by Garret Delaronde on Fri May 10 17:21:50 2013
|
Gian Henriques wrote:
|
|
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: 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. |
|
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: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon May 13 22:31:37 2013
|
David Pilgram wrote:
|
Re: Export entries to XLS or CSV?, posted by Andreas Luedeke on Wed May 15 23:31:30 2013 
|
scogordo wrote:
I've been asked to export one of our logbooks to xls or csv. Doable? |
|
Re: Kerberos on Windows server, posted by Hal Proctor on Thu May 16 16:29:16 2013
|
Hal Proctor wrote:
|
|
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 |