ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67515
|
Wed May 29 08:38:04 2013 |
| UlfO | ulf.olsson@dynamate.se | Question | Windows | 2.9.2-2455 | Filter and sorting |
Hi,
We have a fire preventive team at our company doing periodic inspections of our various corporate buildings.
If they find a deviation they want to register this somewhere.
So I thought E-log would be nice to use in this case.
The way the fire preventive team inspection works is building by building.
All the buildings has numbers.
So they want to be able to select a buildingnumber in E-log and filter on open,ongoing and closed records when they do their inspections.
And they also wants the filtering to stay on that choosen buildingnumber despite if they delete or add new entries.
I know that you can have a default startview in E-log but this view is static.
Is it possible to do this in E-log?
|
67514
|
Tue May 28 19:01:42 2013 |
| Remington Tyler Thornton | rtthornt@indiana.edu | Info | Linux | 2.8-2350 | hyperlink other elog posts |
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 |
67513
|
Tue May 28 09:16:18 2013 |
| Razvan Gornea | gornea@zoho.com | Question | Linux | 2.9.2-2455 | Elog command line problem |
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 ~]
$
|
67512
|
Sat May 25 16:09:58 2013 |
| Norm | normthompson@yahoo.com | Bug report | Windows | Unknown | Re: Application failed to initialize properly |
Andreas Luedeke wrote: |
Norm wrote: |
I attempted to install the newest version of elog on our site elog server from an old old version. Around 2008 I believe. I then received an application failed to initialize properly 0xc0150002 after installing the newest version. I then tried installing the Feb 2013 version and received the same message. Panicked, I rolled back our server to its state yesterday. I would like to update our elog software, anyone know why I am receiving this error??
|
Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed:
- Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475).
- Copy your logbook data to a different PC, maybe your office PC.
- Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using)
- If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.
⇄
Detect language » English
Good luck!
|
Thanks for the reply. I just got back from a business trip and I will try this ASAP. Thanks and I will be posting the error message. |
67511
|
Wed May 22 22:24:14 2013 |
| Hal Proctor | hproctor2@gmail.com | Question | Windows | latest | Admin delete option |
How can I show the Delete option for Admins?
So I have a logbook with the following config:
[Elog]
Admin User = me, otherguy
Deny Change Config File = otherguy
Restrict edit = 1
Restrict edit time = 4
Menu commands = List, New, Edit, Reply,Last Day, Find, Config, Help |
67510
|
Tue May 21 14:33:09 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | Unknown | Re: Application failed to initialize properly |
Norm wrote: |
I attempted to install the newest version of elog on our site elog server from an old old version. Around 2008 I believe. I then received an application failed to initialize properly 0xc0150002 after installing the newest version. I then tried installing the Feb 2013 version and received the same message. Panicked, I rolled back our server to its state yesterday. I would like to update our elog software, anyone know why I am receiving this error??
|
Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed:
- Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475).
- Copy your logbook data to a different PC, maybe your office PC.
- Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using)
- If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.
⇄
Detect language » English
Good luck! |
67509
|
Sat May 18 17:41:51 2013 |
| Norm | normthompson@yahoo.com | Bug report | Windows | Unknown | Application failed to initialize properly |
I attempted to install the newest version of elog on our site elog server from an old old version. Around 2008 I believe. I then received an application failed to initialize properly 0xc0150002 after installing the newest version. I then tried installing the Feb 2013 version and received the same message. Panicked, I rolled back our server to its state yesterday. I would like to update our elog software, anyone know why I am receiving this error?? |
67508
|
Fri May 17 15:26:50 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: some menu commands formed with broken links |
> 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 |