ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 246 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6450 Entries

Goto page Previous 1, 2, 3 ... 245, 246, 247 ... 805, 806, 807 Next

Sun Nov 23 15:19:50 2008

Niall Dooley

Niall_Dooley@inmarsat.com

Stefan Ritt wrote:

Paul O'Shaughnessy wrote:

Can you email a thread of log entries. I think this would be a very useful function, which would enable the logger in effect to send an entire history of a particular issue to the interested parties.

Well, kind of. If you notify yourself with elog entries, they are grouped in a thread in your email application. From there you can forward the thread to someone. Or you forward the link to one entry in the thread, and if the link is the opened, the interested parties see the whole link. Sending the whole thread inside elog is however not possible.

Hi Stefan,

Your suggestion of emailing a link for a log entry with which any interested parties open the link are able to see the entire thread works. However, it does not display the additional text which may be added in the text box below the standard field entries. To view this additional text would require the email recipiant to log into the elog account. The only problem with this is the interested parties may not have the priviledges to log into the elog account. Thanks for your time.

66073

Mon Nov 24 09:50:16 2008

Niall Dooley wrote:

Stefan Ritt wrote:

Paul O'Shaughnessy wrote:

Can you email a thread of log entries. I think this would be a very useful function, which would enable the logger in effect to send an entire history of a particular issue to the interested parties.

Hi Stefan,

You could implemente guest read-only access to the logbook (like for this forum).

66074

Mon Nov 24 13:49:56 2008

Steve Williamson

StephenWilliamson@Barnsley.gov.uk

Bug report

Linux

2.7.5

Re: Special characters in attribute names

Stefan Ritt wrote:

Steve Williamson wrote:

Thanks for elog - it's a brilliant piece of software. I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.

However, I think that I've just discovered my first undocumented 'feature'. Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter. I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.

Quick answer: Don't use '/' in attribute names ;-) but I guess you were kind of afraid to get this answer.

Somehow longer answer: I tried to reproduce your problem with following configuration:

[demo]
Attributes = Author, Type, Subject, Old/New
Options Old/New = Old, New
Quick filter = Type, Old/New

But I was not successful. Everything worked fine using ELOG V2.7.5-2137. Can you please check with the above configuration and tell me exactly when the redirection problem occurs? Is it during filtering on already on creating a new entry?

Thanks for the advice!

I've just had time to set up a test for this using both empty and populated logbooks (which don't have Hardware/Software in every entry as the field was added recently) and newly created logbooks (which have consistent attributes) and saw the problem on .

The control ("Hardware/Software") causing the problem has three options "Hardware Only", "Software Only" and "Both". The problem happens every time you click on the "-- Hardware/Software --" (i.e. All) option in the Quick Filter after having previously selected one (or more) of the options as a filter. This produces the error:

The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept cookies.

I ran elog with a trace (attached) which shows lots of:

select(1024, [5], NULL, NULL, {1, 0}) = 1 (in [5], left {1, 0})
recv(5, "GET /Change_Log/?Hardware%2FSoftware=_all_ HTTP/1.1\r\nHost: localhost:8080\r\nUser-"..., 100000, 0) = 619
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
time(NULL) = 1227528904
send(5, "HTTP/1.1 302 Found\r\nServer: ELOG HTTP 2.7.5-2130\r\nConnection: Keep-Alive\r\nKeep-A"..., 199, 0) = 199
send(5, "<html>redir</html>\r\n", 20, 0) = 20

messages after selecting "-- Hardware/Software --"

The only difference between today's test and last week's is that today the browser is on the local machine.

I also attach my (anonymised) elogd.cfg

Hope this helps

regards

Steve

66075

Mon Nov 24 17:53:23 2008

Re: Special characters in attribute names

Thanks to your detailed description I could reproduce and fix the problem. Please download SVN revision #2144 and give it a try.

66077

Mon Nov 24 18:15:01 2008

Re: Elogd crashes with: *** stack smashing detected ***

Niklas wrote:

Stefan,

perhaps there should be something like the bold text below in elogd.c:

int process_http_request(const char *request, int i_conn)^M
...

   /* extract cookies */^M
   if ((p = strstr(request, "Cookie:")) != NULL) {^M
      p += 6;^M
      do {^M
         p++;^M
         while (*p && *p == ' ')^M
            p++;^M
         strlcpy(str, p, sizeof(str));^M
         for (i = 0; i < (int) strlen(str); i++)^M
            if (str[i] == '=' || str[i] == ';')^M
               break;^M
         if (str[i] == '=') {^M
            str[i] = 0;^M
            p += i + 1;^M
            for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' && i < (int) sizeof(cookie); i++)
cookie[i] = *p++;

...

Wow, where did you get that long cookie from? Certainly not from elogd. You must run elogd under Apache, and have some other service next to it on your server which distributes this long cookies, that's why other people did not experience this problem yet. I appreciate your fix. It's alwasy nice to see users not only complain about things, but try to fix them. Your fix is almost correct, you need a

i<(int) sizeof(cookie)-1

since there is the trailing zero for terminating the cookie string. I applied your fix to SVN revision #2146.

66078

Mon Nov 24 18:16:31 2008

Re: Export of entries

William De La Vega wrote:

I would like to export several entries out of a logbook I have with a specific subject.

I need to send these entries to someone who does not have elog nor can they install it.

Is there a way to do this?

Thanks,

Bill

Yes. Go to the "find" page, select your subject, check "CSV", "XML" or "RAW" and click on search.

66079

Mon Nov 24 20:00:05 2008

Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?

Dennis Seitz wrote:

FYI, I think there's a little bug in the datetime vs $date implementation.

Here's a section of my config file implementing a "Last Edit" field:

Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit

I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.

I found that using this instead works:
Preset Last Edit =$entry time

which seems contradictory since
Subst on edit Last Edit = $date
works fine.

Do you have an old version of elog? Using the current version with a configuration file:

Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit

I get the correct behavior:

66080

Tue Nov 25 17:01:55 2008

Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?

Stefan Ritt wrote:

Dennis Seitz wrote:

Do you have an old version of elog? Using the current version with a configuration file:

Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit

I get the correct behavior:

Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome.

Goto page Previous 1, 2, 3 ... 245, 246, 247 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6