ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68172
|
Fri Oct 30 15:52:33 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.1 | Re: propogating messages through logbooks | > Hi there
>
> Okay so let me explain what im trying to do. I have a table in a logbook (lets call it home) that the user fills
> out. This information in the table is related to other logbooks (8 of them to be exact).
> I want to propogate information from the table in the home logbook into the other logbooks. To do this I used
> Execute new which runs my scripts. One of the scripts makes a call to the elog
> client to submit the message. The problem is that this call to elog client never finishes because its hanging
> waiting for the initial submit (one which triggered Execute new) to finish. The documentation
> explained that only one submit can be processed at a time so i expected whats happening at the moment.
>
> My question is are there any other ways to do what im trying to do?? In a nutshell how to propogate information
> from one logbook to another autonomously.
>
> Regards
> Kenzo
Hi Kenzo,
I think it would help me to understand your problem, if you would provide a minimal configuration file with two
logbooks.
There is no ELOG internal feature to propagate data from one logbook to another;
using a shell script is the only method I know.
But you could easily put your script into the background:
ELOG can handle multiple parallel request, by handling one request after the other.
Kind Regards, Andreas |
68176
|
Mon Nov 2 08:41:20 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 3.1.1 | Re: restrict edit time and autosave | Hi Kester,
yes, I did run into the same problem, that I could not even delete old drafts due to our restrict edit time.
We allow anonymous submissions in our operation logbooks. After a while drafts of unsubmitted messages just pile up; and I need to remove them as administrator.
While I can do that easily for anonymous drafts, I cannot do that for drafts of other users: I don't easily see those drafts.
It would be really nice, if drafts would be handled different then other entries regarding "Restrict edit time" as you've suggested.
Cheers, Andreas
Kester Habermann wrote: |
Hello,
When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after the autosave. If the time is up, it is no longer possible to submit the report.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103
Regards
Kester
|
|
68178
|
Wed Nov 4 14:40:39 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2 | Re: WYSIWYG editor for Elog not working in Debian Jessie | Hi Nicola,
this appears to be a particular problem of the specific (outdated) ELOG debian package.
But you could just download the FCKeditor directly and install it to the proposed location "/usr/share/fckeditor".
Or you download ELOG 3.1.1 and give it a try to install it with the makefile.
Cheers, Andreas
Nicola wrote: |
I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:
root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25 2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory
Is this a Deban misconfiguration or a bug in Elog? thanks
|
|
68183
|
Mon Nov 9 10:33:46 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2 | Re: WYSIWYG editor for Elog not working in Debian Jessie | Hi Nicola,
as Stefan pointed out: the debian package that you are using is from an outdated ELOG version and not supported anymore. I can't help you with that.
Is somebody out there that created a 3.1.x version debian package?
Cheers, Andreas
Nicola wrote: |
Hi Andreas, I opted for the first solution since the Debian package, although outdated and broken, has some goodies like a systemd unit for managing the daemon which is very handy. I downloaded FCKeditor 2.6.11 from SourceForge (after a long search, seems that CKeditor made its parent almost disappear from the web), unpacked it in the proper folder and not the WYSIWYG editor works. I have just a couple of minor issues: there is no attachment drop area (I had it in my old Debian 6 server) and the editor toolbar has an ugly "Windows 95" look; see the attached image. I can live with these problems but if the can be easily fixed then obviously I would do that, can you give me any hint? Thank you very much.
Andreas Luedeke wrote: |
Hi Nicola,
this appears to be a particular problem of the specific (outdated) ELOG debian package.
But you could just download the FCKeditor directly and install it to the proposed location "/usr/share/fckeditor".
Or you download ELOG 3.1.1 and give it a try to install it with the makefile.
Cheers, Andreas
Nicola wrote: |
I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:
root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25 2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory
Is this a Deban misconfiguration or a bug in Elog? thanks
|
|
|
|
68195
|
Fri Nov 20 11:06:24 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.1 | Re: log entries after a certain date not displayed - 3.1.1 | Hi Mike,
I don't think that it is a good idea to have two elogd servers accessing the same files: that's what you are doing with the Dropbox folder, isn't it? ELOG is not made to be used like that.
If you want to share the same entries in different logbooks, then you should use the "mirror server" functionality in ELOG. Have a look at: https://midas.psi.ch/elog/config.html#mirroring
Cheers, Andreas
Mike Giles wrote: |
Hi,
I'm having an issue with Elog 3.1.1 on windows 10 not displaying all log entries (after a certain date) in a logbook directory.
The logbook is saved in a Dropbox folder and the entries were created on a windows 8.1 PC with 3.1.1 also.
I created an entry in windows 10, this created a new log file (new day) with a duplicate ID, deleted the log file and then the windows 10 pc displayed all entries.
Is there any way to ensure Elogd picks up all log files ?
Thanks & Regards,
Mike
|
|
68209
|
Fri Dec 11 14:30:10 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | Other | 3.1.1-bc8310a | Re: If a Required Attribute starts with a number – No CKEditor | Hi David,
I can confirm a bug: changing the encoding does not work if you have a required attribute starting with a digit. The following minimal config reproduces the bug:
[global]
Default encoding = 1
[test]
Attributes = 7SWM
Options 7SWM = Name
Required Attributes = 7SWM
Whatever you choose as a default encoding you'll be stuck with. If you remove the "Required Attributes" it works again.
The workaround is very simple: do not use any attributes that do start with a digit :-)
Cheers, Andreas
David Dunne wrote: |
Hello, Is the below an issue or am I doing something incorrectly? Creating an attribute starting with a number and then including that attribute in the Required Attribute list prevents access to the CKEditior. This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows 7 with Elog V3.1.1-3f311c5. The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing below. While attribute 7SWM is part of the Required Attributes the CKEditor fails to appear, remove 7SWM from the Required Attributes list and the CKEditor returns. [global] port = 8080 [demo] Theme = default Comment = General Linux Tips & Tricks Attributes = Author, Type, Category, Subject, 7SWM Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Other Options 7SWM = Name-1, Name-2, Name-3 Extendable Options = Category Required Attributes = Author, Type, 7SWM Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Type Thank you, David Dunne |
|
68211
|
Wed Dec 16 09:56:09 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
68214
|
Tue Jan 12 11:48:57 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Linux | V3.1.0-2411f95 | Re: Prefill attributes for new post | Hi Johan,
yes, it is possible. And you were actually very close :-)
In order to pass preset-parameters within a URL, you just need to prefix the fieldname with a "p". In your example, you would write "...&pSubsystems=Vacuum".
Here is an example for the Linux Demo logbook:
https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&pAuthor=Santa+Claus&pSubject=Christmas+Presents&pType=Problem+Fixed&pCategory=Hardware
This feature is even already documented: https://midas.psi.ch/elog/userguide.html#misc :-)
I wish you a Happy New Year!
Andreas
Johan Forsberg wrote: |
Hi all,
I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.
To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already filled out to "Vacuum".
Is this possible already? I've tried naively using URL parameters (e.g. "&Subsystem=Vacuum") but that does not work. If it's not implemented, I think it would be a useful feature to have (and quite important for my particular use case). I could create a new post first using the "elog" tool, with the desired attributes set, but it makes more sense to defer the actual creation of the post to the user, i.e. he/she might change their mind before pressing "submit".
Thanks,
Johan Forsberg, MAX IV Laboratory, Sweden
|
|
|