Re: Special characters in attribute names, posted by Stefan Ritt on Mon Nov 17 10:18:52 2008
|
| Steve Williamson wrote: |
|
Hi
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?
|
Re: Special characters in attribute names, posted by Steve Williamson on Mon Nov 24 13:49:56 2008 
|
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Hi
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
|
|
Re: Special characters in attribute names, posted by Stefan Ritt on Mon Nov 24 17:53:23 2008
|
Thanks to your detailed description I could reproduce and fix the problem. Please download SVN revision #2144 and give it a try. |
|
Re: Special characters in attribute names, posted by Steve Williamson on Wed Nov 26 12:49:08 2008
|
| Stefan Ritt wrote: |
|
Thanks to your detailed description I could reproduce and fix the problem. Please download SVN revision #2144 and give it a try.
|
Tested SVN v 2147 and all looks OK
thanks
Steve |
|
Re: Spec file change, posted by Stefan Ritt on Tue May 9 08:07:00 2006
|
| Stephen A. Wood wrote: | | Could the "Copyright:" line in the elog.spec file be changed to "License:" for the next release? Without this change an RPM can't be built on FC4 (RPM 4.4.1). With the change, rpms can still be built in Enterprise linux 3 (RPM 4.2.3). |
Wow, the RPM build depends on that name? Interesting. I changed it in the SVN version, so it will be contained in the next release. |
|
Re: Space in logbook name with password list results in "List" menu acting strange, posted by Stefan Ritt on Tue Feb 22 10:35:17 2005
|
> If you have a space in a logbook name and you enable password list, then
> the "List" menu option forces you to the login page each time.
> The URL says "aaa+bbb", but when you do not have passwords enabled, the
> URL is "aaa bbb"
Thanks for reporting this. I fixed it in the current CVS version. |
|
Re: Sorting by numeric attribute (not entry ID)., posted by Stefan Ritt on Tue Jun 4 12:03:18 2013
|
> By default, elog enties are sorted by their ID number. When viewing a logbook in Full or Summary, they are
> shown in strict order of ID. In Threaded, entries are shown in strict order of ID for the latest entry of each
> thread, and then previous entries (in reply to) back from the latest one.
>
> In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> last" chosen, but that's a detail).
>
> I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter.
>
> Now this works fine in Full or Summary mode. In threaded mode (e.g. default for this forum, where every entry
> is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> entry it is in reply to, but all just slightly offset to the first entry.
>
> If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't. Looks
> (almost) the same as threaded.
>
> I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> I cannot seem to get this to happen. Have I missed something here? Or is it possible at all?
This is not possible at the moment, but I will add it to the wish list. |
|
Re: Sorting by numeric attribute (not entry ID)., posted by David Pilgram on Tue Jun 4 15:00:23 2013
|
> > By default, elog enties are sorted by their ID number. When viewing a logbook in Full or Summary, they are
> > shown in strict order of ID. In Threaded, entries are shown in strict order of ID for the latest entry of each
> > thread, and then previous entries (in reply to) back from the latest one.
> >
> > In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> > last" chosen, but that's a detail).
> >
> > I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter.
> >
> > Now this works fine in Full or Summary mode. In threaded mode (e.g. default for this forum, where every entry
> > is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> > doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> > entry it is in reply to, but all just slightly offset to the first entry.
> >
> > If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't. Looks
> > (almost) the same as threaded.
> >
> > I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> > I cannot seem to get this to happen. Have I missed something here? Or is it possible at all?
>
> This is not possible at the moment, but I will add it to the wish list.
OK, Thanks Stefan. |
|