ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66176
|
Tue Jan 27 09:19:22 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 2.7.5 | Re: convert: unrecognized option '-set' | > Hello,
>
> We are now running elog-2.7.5 in a Scientific Linux 4 (RHEL4) system, which uses ImageMagick 6.0.7.1. After uploading an image, the image
> manipulation buttons don't work and complain:
> convert: unrecognized option '-set'
>
> We are using an RPM built from source, and it looks like I should be able to just change "-set comment ..." to "-comment" as in:
> ------
> [dab66@lnx100 tmp]% diff elogd.c elogd.c.new
> 22601c22601
> < sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -set comment ' %d' '%s'", file_name, new_rot,
> ---
> > sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -comment ' %d' '%s'", file_name, new_rot,
> 22607c22607
> < sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -set comment ' %d' '%s'", file_name, new_rot,
> ---
> > sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -comment ' %d' '%s'", file_name, new_rot,
> 22618c22618
> < sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -set comment ' %d' '%s'", file_name, cur_rot,
> ---
> > sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -comment ' %d' '%s'", file_name, cur_rot,
> 22624c22624
> < sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -set comment ' %d' '%s'", file_name, cur_rot,
> ---
> > sprintf(cmd, "convert '%s' -rotate %d -thumbnail %d -comment ' %d' '%s'", file_name, cur_rot,
> ------
>
> Is there any better way for us to fix this, or is anything else needed?
Well, I believe your modification won't work. I just tried it with ImageMagick 6.3.8 and it failed. Try to rotate your picture four times, and
it should be back to the old position. When I use "-comment" instead "-set comment" on a PNG file, this did not work. From the man page it
tells me:
Version: ImageMagick 6.3.8 01/25/08 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2008 ImageMagick Studio LLC
Usage: convert [options ...] file [ [options ...] file ...] [options ...] file
Image Settings:
...
-comment string annotate image with comment
...
Image Operators:
...
-set property value set an image property
...
So indeed "-comment" and "-set comment" are two different things. I'm afraid you have to upgrade your ImageMagick package in order to make
this work. |
66177
|
Tue Jan 27 12:30:26 2009 |
| Carsten Elftmann | Carsten.Elftmann@BkiTech.de | Question | Windows | 2.7.5-2130 | Re: Error Message in HTML or Java Script alert |
Stefan Ritt wrote: |
Carsten Elftmann wrote: |
I have there a problem with the error message at required attributes.
I have two logbooks with identical settings,
in one the errror message appears as Javascript Alert,
in the other one as html-page, and after using the back button the entered text disapear.
Same I have in this forum.
|
Can you describe what you exactly enter in this forum to produce the error so that I can reproduce it?
|
I could not produce this error here again, so I work on that:
There was a attribute with Type = Date, Preset = $Date.
This added following js code
for (var i=0 ; i<document.form1.y0.value.length ; i++) if ((document.form1.y0.value.charAt(i) < "0" || document.form1.y0.value.charAt(i) > "9")) { break }
This cause in following error
Fehler: document.form1.y0 is undefined Quelldatei: http://elog1.bkitech.de/Test-Maengelbericht/?cmd=Neu Zeile: 16
After that error none js will be executed.
After remarking the Type line, all work well.
|
66179
|
Tue Jan 27 15:45:52 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2-7-5 | Re: Last day -- list menu command |
Mike Forster wrote: |
Hi folks,
I want to have Last day be a command in the List display, so I added:
List menu commands = New, Find, Import, Login, Logout, Config, Last day, Help
However, when Last day is selected, the command does not change to Last 2 days.
What is the right way to do this?
|
You have to put "Last x" in the menu, not "Last day". Unfortunately by default the label "Last day" does not show up. I fixed this in the current version. But you can yourself start this thing by adding "past1" to the URL, or by making yourself a bookmark in your browser. Like
https://midas.psi.ch/elogs/Forum/past1
then the "Last 2 days" will show up. |
66181
|
Tue Jan 27 16:01:09 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | last one | Re: Is it possible to generate an ID with a particular format ? |
Franck C wrote: |
Hi,
I want to know if it is possible to display an ID with this format: YYYY-XXXX where YYYY is the current year and XXXX a sequential number from 0001 to 9999 ?
ID Display = 2009$message id
could be fine but the year is hard coded and there are no 0 before the number.
Can you help me ?
Thanks a lot 
|
You cannot make this with the ID, but you can create an additional attribute which will show exactly this behavior. Have a look under
subst <attribute> = %Y-####
in the documentation. |
66182
|
Tue Jan 27 17:29:24 2009 |
| Mike Forster | mike4ster@gmail.com | Question | Linux | 2-7-5 | Re: Last day -- list menu command |
Stefan Ritt wrote: |
Mike Forster wrote: |
Hi folks,
I want to have Last day be a command in the List display, so I added:
List menu commands = New, Find, Import, Login, Logout, Config, Last day, Help
However, when Last day is selected, the command does not change to Last 2 days.
What is the right way to do this?
|
You have to put "Last x" in the menu, not "Last day". Unfortunately by default the label "Last day" does not show up. I fixed this in the current version. But you can yourself start this thing by adding "past1" to the URL, or by making yourself a bookmark in your browser. Like
https://midas.psi.ch/elogs/Forum/past1
then the "Last 2 days" will show up.
|
Thanks very much, Stefan.
I did not know "Last x" was the appropriate menu option.
--Mike |
66183
|
Wed Jan 28 14:38:52 2009 |
| Michael Ambrus | ambrmi09@gmail.com | Bug report | Windows | 2.7.5 | Re: Stack error when email notification is active |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Michael Ambrus wrote: |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries?
|
Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.
Windows binaries also solved the issue with the "Top grop" in my other bug rapport.
Thanks for the help!
|
Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.
The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:
Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6
The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?
It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.
Regards /Michael
|
The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.
Furthermore, TLS is not supported in elogd, only plain SMTP is possible.
|
Thanks for the info, it saves me some time know this on beforehand.
You're right about the Windows binary, it's a lower SVN revision (2140).
|
66184
|
Wed Jan 28 14:39:56 2009 |
| Michael Ambrus | ambrmi09@gmail.com | Bug report | Windows | 2.7.5 | Re: Stack error when email notification is active |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Michael Ambrus wrote: |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries?
|
Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.
Windows binaries also solved the issue with the "Top grop" in my other bug rapport.
Thanks for the help!
|
Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.
The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:
Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6
The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?
It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.
Regards /Michael
|
The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.
Furthermore, TLS is not supported in elogd, only plain SMTP is possible.
|
Thanks for the info, it saves me some time know this on beforehand.
You're right about the Windows binary, it's a lower SVN revision (2140).
|
66186
|
Mon Feb 2 09:46:24 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2168 | Re: Incrementation of attribute is not functioning, help needed to fix this. |
Guido Böing wrote: |
I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...
Below is my configuration (at least the part that gives me headaches..)
[Onderhoud Diversen]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2
|
I tried your configuration and got the attribute incrementing correctly:
so I'm a bit at a loss, too. Maybe your browser caches the old page, so try a "Reload" on your browser or clear your cache. Maybe your logbook contains some weird entries which make the incementing break. Try this configuration with an empty logbook. Certainly the configuration options are correct. |
|