ELOG Forum

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers

Andreas

Dear Andreas,

thank you very much for your prompt reply and for you suggestions, which helped me to solve the problem. Now it's all working perfectly.

Cheers,

Paolo

67658

Tue Jan 21 13:17:52 2014

Re: [Not] Submit on pressing enter key

Daniel Campora wrote:

Hello community,

I have a feature request for the form of the ELOG.

For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.

Cheers, keep up the good work,

Daniel

Have a look at this forum. If you press <enter> on the subject field, you get asked "do you really want to submit this entry" and you have the chance to cancel and continue editing. You should get the same with the current elog version.

Attachment 1: Screen_Shot_2014-01-21_at_13.16.48_.png

67659

Fri Jan 24 18:59:17 2014

Re: Crash report involving propagate and replies

Stefan Ritt wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?

/Stefan

Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.

PS. If anyone else has managed to compile this could you give me a hand =)

67660

Wed Jan 29 17:13:55 2014

Re: Crash report involving propagate and replies

Stephen wrote:

Stefan Ritt wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

/Stefan

Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.

PS. If anyone else has managed to compile this could you give me a hand =)

This resolved the issue, thanks for the help. I have tested it on server machines and was able to go over 10 each time.

Thank you for resolving this issue for me.

67661

Mon Feb 3 22:45:10 2014

Re: Crash report involving propagate and replies

Stephen wrote:

Stefan Ritt wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

/Stefan

Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.

PS. If anyone else has managed to compile this could you give me a hand =)

I was able to manage and compile the latest code from GIT. It runs fine so far. Just a hint, in order to compile successfully, there are some steps that you may need to modify your header file depend on how you store your mxml, krb5, OpenSSL files and directories.

67664

Thu Feb 20 16:36:06 2014

Re: Adaptation of the language

Markus Grosse-Kock wrote:

Hello,

I want to change the language to German. But it does not work.

Here my config:

Theme = default
Resource dir = D:\Elog
Language = german

Where is the problem? Or is it not possible to change the language in Windows?

Best regards,

Markus

You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.

Viele Grüsse nach Reken,
Stefan

67666

Fri Feb 21 13:09:48 2014

Re: Unable to resize images in browser

Matthew Deller wrote:

I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.

Output when running elog with verbose option shows buffer overflow when resize attempted:

[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated

Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick?

What happens if you execute the command manually, like

$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png

The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.

/Stefan

67667

Fri Feb 21 13:25:55 2014

Re: Export entries to XLS or CSV?

Andreas Luedeke wrote:

Jim Tinlin wrote:

Stefan Ritt wrote:

Andreas Luedeke wrote:

Yes, you're right: the text field is only exported in XML and Raw mode.

It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.

But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.

I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.

(This string has not yet been added to the localization.)

As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.

Of course the spreadsheet programs just display the HTML source.

Stefan, do you think this should be added to the official branch?

⇄

Detect language » English

⇄

Detect language » English

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.

Has this been added yet?

I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.

Thanks!

Hi Jim, I've incorporated the patch to our production server about a week ago.

I've agreed with Stefan that he'll add it, when it proved to run stable for a while.

Until now it appears to work fine. I think Stefan will add it to the distribution soon.

But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.

Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,

the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c

⇄

Detect language » English

Andreas

⇄

Detect language » English

⇄

Detect language » English

⇄

Detect language » English

This patch is now officially in the GIT repository.

Goto page Previous 1, 2, 3 ... 375, 376, 377 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6