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. |
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.
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.
[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config
user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them). Is there a way after user1 click save, page doesn't go to that config page?
I could put
Deny Change password =
Deny Remove user
Deny New user
so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page.
|
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. |
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 |
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: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon May 13 22:31:37 2013
|
David Pilgram wrote: |
[...]
As for the computer time switching, I am aware of the issues, it's a stand-alone linux box, I've found elog to be surprisingly tolerant, everything's backed up. The introduction of a 'When' attribute had better be on new logbooks or introduced at end of year (esp during quiet time) so that existing books don't fail to find what I'm looking for in searches.
[...]
|
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 :-)
Cheers
Andreas
 ⇄
Detect language » English
|
Export entries to XLS or CSV?, posted by scogordo on Wed May 15 17:24:12 2013
|
I've been asked to export one of our logbooks to xls or csv. Doable?
Thanks,
Scott |
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?
Thanks,
Scott
|
Hi Scott,
yes, every user can export entries using the "find" command.
Just select the export format in the first line
Export to:
  ⇄
Detect language » English
⇄
Detect language » English
I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.
I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.
There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format. |
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? |
|