ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68590
|
Wed Apr 5 13:16:34 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.0-3c6435e | Re: Elog not see image magick |
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
christian wrote: |
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
68591
|
Thu Apr 6 11:01:30 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Windows | 3.1.2 | Re: pre defined Find as Home page |
It's very simple, no need for the find command. E.g.: Start page = ?Author=luedeke&Category=Question&mode=summary
in this forum would do https://midas.psi.ch/elogs/Forum/?Author=luedeke&Category=Question&mode=summary
Paraic Fahey wrote: |
This command makes the Homepage a FIND page: Start page = ?cmd=Find
My question is: can we pre-populate some of the search fields and execute the search so that the homepage becomes the SEARCH RESULTS
|
|
68593
|
Fri Apr 7 09:58:33 2017 |
| christian | c_grebing@web.de | Question | Windows | V3.1.0-3c6435e | Re: Elog not see image magick |
This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.
Christian
Stefan Ritt wrote: |
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
christian wrote: |
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
|
68594
|
Fri Apr 7 10:22:03 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.0-3c6435e | Re: Elog not see image magick |
I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.
Stefan
christian wrote: |
This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.
Christian
Stefan Ritt wrote: |
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
christian wrote: |
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
|
|
68595
|
Fri Apr 7 10:24:31 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.0-3c6435e | Re: Elog not see image magick |
Ah sorry. I recall now: Under Windows, calling subprocesses from a service does not work at all. After a couple of days of work I was not able to get this running. If somebody has some idea, I'm happy to try it. So most people use the elogd daemon in the background only under Linux.
Stefan
Stefan Ritt wrote: |
I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.
Stefan
christian wrote: |
This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.
Christian
Stefan Ritt wrote: |
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
christian wrote: |
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
|
|
|
68596
|
Fri Apr 7 11:46:09 2017 |
| christian | c_grebing@web.de | Question | Windows | V3.1.0-3c6435e | Re: Elog not see image magick |
Ok, this explains why it doesn't work.
Thank you for the support anyway. ELOG is a great piece of software.
Christian
Stefan Ritt wrote: |
Ah sorry. I recall now: Under Windows, calling subprocesses from a service does not work at all. After a couple of days of work I was not able to get this running. If somebody has some idea, I'm happy to try it. So most people use the elogd daemon in the background only under Linux.
Stefan
Stefan Ritt wrote: |
I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.
Stefan
christian wrote: |
This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.
Christian
Stefan Ritt wrote: |
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
christian wrote: |
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
|
|
|
|
68598
|
Tue Apr 11 17:24:48 2017 |
| Francois Cloutier | Francois@fcmail.ca | Question | Windows | 3.1.2-7933898 | rename menu commands |
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help ! |
68599
|
Tue Apr 11 18:05:15 2017 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 3.1.2-7933898 | Re: rename menu commands |
Hi,
First up, the Copy command is supposed to be used to copy to another log book, as it says in the documentation, not a duplicate entry in the same logbook. I've tried doing a copy into the same logbook, it appears to work (although I don't know about every circumstance, I just did a quick and dirty test). Use at your own risk! Don't use Preserve ID feature is one caution I would raise immediately.
As for renaming the command, I'd suggest defining a new language, "lenglish" or whatever, make all the files necessary as per any normal language; in the eloglang.lenglish file would be
New = New
Edit = Modify
---
Copy to = Duplicate
and so on. I chose to call my eloglang "lenglish" as duplicate, modify etc as used in the example here derive from Latin, but other commands would still be English.
When specified in the config file (just like the languages that "come with the box") that should give you the alternative names for the commands.
David.
Francois Cloutier wrote: |
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help !
|
|